Triple
T7137667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyland |
E166348
|
entity |
| Predicate | hasProtagonistResidence |
P70690
|
FINISHED |
| Object | Noddy’s house in Toy Town |
—
|
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: Noddy’s house in Toy Town | Statement: [Toyland, hasProtagonistResidence, Noddy’s house in Toy Town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistResidence Context triple: [Toyland, hasProtagonistResidence, Noddy’s house in Toy Town]
-
A.
hasResidenceFeature
Indicates that a residence possesses or is characterized by a specific feature or attribute.
-
B.
favoriteResidenceOf
Indicates that a particular residence is the one most preferred or liked by a given person or entity among all residences associated with them.
-
C.
fictionalResidence
Indicates that one entity is the place where another entity lives or is based within a fictional or imaginary context.
-
D.
isResidentialBaseFor
chosen
Indicates that a location serves as the primary place of residence or home base for a person or group.
-
E.
houseLocatedIn
Indicates that a house is situated within or belongs to a specific geographic location or area.
- 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e6939b788190929e92ff481f2ee4 |
completed | March 27, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:45 p.m.