Triple
T18167755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ἡφαιστίων |
E434937
|
entity |
| Predicate | relationshipTypeWithAlexander |
P10690
|
FINISHED |
| Object | intimate companion |
—
|
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: intimate companion | Statement: [Ἡφαιστίων, relationshipTypeWithAlexander, intimate companion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeWithAlexander Context triple: [Ἡφαιστίων, relationshipTypeWithAlexander, intimate companion]
-
A.
relationshipToMorganAlexander
Indicates the specific type of relationship or connection an entity has to Morgan Alexander.
-
B.
hasRelationshipTypeWith Alexandra Bergson
Indicates that there exists a specific type or category of relationship between an entity and Alexandra Bergson.
-
C.
relationshipType
chosen
Indicates the specific kind of relationship that exists between two or more entities.
-
D.
historicalRelationship
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
-
E.
relationshipToRa
Indicates a specified type of relational connection that an entity has to the entity Ra.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4df52f8b08190ab2c4d76b510cd28 |
completed | April 19, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.