Triple
T5165404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The LINQ Hotel + Experience |
E116538
|
entity |
| Predicate | positionOnStrip |
P38325
|
FINISHED |
| Object | mid-Strip |
—
|
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: mid-Strip | Statement: [The LINQ Hotel + Experience, positionOnStrip, mid-Strip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnStrip Context triple: [The LINQ Hotel + Experience, positionOnStrip, mid-Strip]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
positionInBand
Indicates the specific role or place an individual holds within a musical band.
-
C.
positionOnLine
chosen
Indicates that one entity occupies a specific location along a defined line or linear path in relation to another.
-
D.
positionNumber
Indicates the specific ordinal or identifying number assigned to a position within an ordered set or organizational structure.
-
E.
positionOnGood
Indicates the stance or viewpoint an entity holds regarding a particular good, such as support, opposition, or neutrality.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd792af4648190934cf2db523f6921 |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.