Triple
T6150652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tooth Fairy |
E137190
|
entity |
| Predicate | exchangeFor |
P27066
|
FINISHED |
| Object | money |
—
|
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: money | Statement: [Tooth Fairy, exchangeFor, money]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exchangeFor Context triple: [Tooth Fairy, exchangeFor, money]
-
A.
exchangedFor
chosen
Indicates that one entity has been traded or substituted in return for another entity.
-
B.
exchangeSegmentOf
Indicates that one entity gives a portion or segment of something to another entity, typically as part of a reciprocal transfer or trade.
-
C.
exchangeSegment
Indicates a relationship where one entity trades or swaps a defined portion or segment of something with another entity.
-
D.
exchangeCode
Indicates a relationship where one entity trades or swaps a code with another entity, typically to obtain access, authorization, or some corresponding value in return.
-
E.
exchangeAuthority
Indicates a relationship where control or decision-making power is transferred or swapped between entities.
- 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_69c008a45d008190832a9e19f5d63406 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05ce329648190a03ba0233df841fa |
completed | March 22, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.