Triple
T12227191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telamon |
E291382
|
entity |
| Predicate | relationToAchilles |
P94755
|
FINISHED |
| Object | uncle |
—
|
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: uncle | Statement: [Telamon, relationToAchilles, uncle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToAchilles Context triple: [Telamon, relationToAchilles, uncle]
-
A.
relationToWinner
Indicates the specific relationship or connection an entity has to the winner of a contest, competition, or event.
-
B.
relationshipToRelative
chosen
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
C.
relationToAncestors
Indicates a familial relationship that connects an entity to one or more of its ancestors in a lineage or hierarchy.
-
D.
relationToTheIndependent
Indicates a relationship in which one entity is connected or relevant to another entity that is designated as independent.
-
E.
relativeToCorinthian
Indicates a relationship defined in terms of Corinthian as a reference point, such as position, orientation, or relevance relative to Corinthian.
- 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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d924a3973c8190a882046963b320fb |
completed | April 10, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69d91c41bcbc81909782f4e3c571b218 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.