Triple
T20000167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tobias |
E494298
|
entity |
| Predicate | relationshipToHarryAndEdna |
P131072
|
FINISHED |
| Object | longtime friend |
—
|
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: longtime friend | Statement: [Tobias, relationshipToHarryAndEdna, longtime friend]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToHarryAndEdna Context triple: [Tobias, relationshipToHarryAndEdna, longtime friend]
-
A.
relationshipToHarry
chosen
Indicates the specific type of relationship or connection that an entity has to Harry.
-
B.
relationshipToHarryMonroe
Indicates the specific type of personal, social, or familial relationship that one entity has to Harry Monroe.
-
C.
relationshipToEdnaTurnblad
Indicates the specific familial, social, or personal connection that one entity has to Edna Turnblad.
-
D.
relationshipToEdwardBloom
Indicates the nature or type of connection an entity has to Edward Bloom, such as familial, social, or other relational ties.
-
E.
relationshipToHarryBright
Indicates that one entity has a specified personal or familial relationship to the person identified as Harry Bright.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a15f308190a99ac3205f948acb |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:32 p.m.