Triple
T24274852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Dyer Stand |
E605378
|
entity |
| Predicate | namedFacilityType |
P155630
|
FINISHED |
| Object | stand |
—
|
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: stand | Statement: [Jack Dyer Stand, namedFacilityType, stand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedFacilityType Context triple: [Jack Dyer Stand, namedFacilityType, stand]
-
A.
isNamedFacilityOf
Indicates that a facility bears the official name associated with a particular entity (such as an organization, person, or place).
-
B.
designedFacilityType
Indicates the type or category of facility that something (such as a plan, system, or component) is specifically designed for.
-
C.
fccFacilityType
Indicates the specific type or classification of a facility as defined by the FCC (Federal Communications Commission).
-
D.
primaryFacilityType
Indicates the main or predominant type or category of facility associated with an entity.
-
E.
identifiesFacility
Indicates that one entity serves to recognize, specify, or distinguish a particular facility as the relevant or associated one.
- F. None of above. chosen
Provenance (4 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d5da53c8190810f4e7777d112ba |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 18, 2026, 12:07 a.m.