Triple
T17541895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WSH |
E427217
|
entity |
| Predicate | identifiesFacilityType |
P2836
|
FINISHED |
| Object | space shuttle landing site |
—
|
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: space shuttle landing site | Statement: [WSH, identifiesFacilityType, space shuttle landing site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiesFacilityType Context triple: [WSH, identifiesFacilityType, space shuttle landing site]
-
A.
fccFacilityType
Indicates the specific type or classification of a facility as defined by the FCC (Federal Communications Commission).
-
B.
hasFacilityType
chosen
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
C.
designedFacilityType
Indicates the type or category of facility that something (such as a plan, system, or component) is specifically designed for.
-
D.
primaryFacilityType
Indicates the main or predominant type or category of facility associated with an entity.
-
E.
usedAtFacilityType
Indicates that something is utilized or applied within a facility of a specified type.
- 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_69d889df6dc081908f67dbadc03c07ee |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4545e64448190a2a63bc13f549027 |
completed | April 19, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.