Triple
T29340133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Tentacle |
E744013
|
entity |
| Predicate | houseLocationInGame |
P162000
|
FINISHED |
| Object | inside the Edison mansion |
—
|
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: inside the Edison mansion | Statement: [Green Tentacle, houseLocationInGame, inside the Edison mansion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: houseLocationInGame Context triple: [Green Tentacle, houseLocationInGame, inside the Edison mansion]
-
A.
houseLocatedIn
Indicates that a house is situated within or belongs to a specific geographic location or area.
-
B.
housePosition
chosen
Indicates the spatial location or placement of a house relative to a reference point or area.
-
C.
homeLocationInStory
Indicates the place that serves as a character’s primary home or base of residence within the context of the story.
-
D.
locationProperty
Indicates that one entity specifies or characterizes a locational attribute or spatial property of another entity.
-
E.
gameLocation
Indicates the place or venue where a game or match takes place.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 1:33 p.m.