Triple
T31425461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liza |
E801649
|
entity |
| Predicate | relationshipTypeWithHermann |
P138067
|
FINISHED |
| Object | romantic interest |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: romantic interest | Statement: [Liza, relationshipTypeWithHermann, romantic interest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeWithHermann Context triple: [Liza, relationshipTypeWithHermann, romantic interest]
-
A.
relationshipToHermann
chosen
Indicates the specific familial, social, or professional relationship that one entity has to the person named Hermann.
-
B.
relationshipToHermaphroditus
Indicates the specific familial, romantic, or social relationship that one entity has to Hermaphroditus.
-
C.
relationshipToHenry
Indicates the specific type of relationship or connection that an entity has to Henry.
-
D.
relationshipTypeWithWilhelm Meister
Indicates the specific type or nature of the relationship that an entity has with Wilhelm Meister.
-
E.
heraldicRelationship
Indicates a relationship between entities expressed through heraldic symbolism, such as coats of arms, crests, or heraldic devices.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 8:52 p.m.