Triple
T1401129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyler |
E30784
|
entity |
| Predicate | operatesAtLocation |
P794
|
FINISHED |
| Object | entrance_of_lodge_room |
—
|
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: entrance_of_lodge_room | Statement: [Tyler, operatesAtLocation, entrance_of_lodge_room]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesAtLocation Context triple: [Tyler, operatesAtLocation, entrance_of_lodge_room]
-
A.
operatedAt
Indicates that an operation, procedure, or activity was performed at a specific location or facility.
-
B.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
-
C.
operatesWithin
chosen
Indicates that one entity carries out its activities, functions, or operations inside the scope, boundaries, or jurisdiction defined by another entity.
-
D.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
E.
trainingFacilityLocation
Indicates the place or site where a training facility is situated 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c39da20c8190b9c82cc4ad747c66 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.