Triple
T6150650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tooth Fairy |
E137190
|
entity |
| Predicate | typicalLocationOfAction |
P30151
|
FINISHED |
| Object | child's bedroom |
—
|
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: child's bedroom | Statement: [Tooth Fairy, typicalLocationOfAction, child's bedroom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLocationOfAction Context triple: [Tooth Fairy, typicalLocationOfAction, child's bedroom]
-
A.
placeOfEffect
chosen
Indicates the location or setting where an action, event, or effect takes place or is realized.
-
B.
typicalGameLocation
Indicates the usual or characteristic place where a game is played or takes place.
-
C.
notableAttackLocation
Indicates the specific place where a significant or notable attack occurred in relation to the subject.
-
D.
possiblePlaceOfMission
Indicates that a location is a plausible or candidate site where a mission may have taken place or could take place.
-
E.
typicalUseLocation
Indicates the usual or most common location where an entity is used or operates.
- 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.