Triple
T36485590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbus External Payload Facility |
E898924
|
entity |
| Predicate | hasPayloadSite |
P5003
|
FINISHED |
| Object | Starboard Zenith site |
—
|
NE NERFINISHED |
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: Starboard Zenith site | Statement: [Columbus External Payload Facility, hasPayloadSite, Starboard Zenith site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPayloadSite Context triple: [Columbus External Payload Facility, hasPayloadSite, Starboard Zenith site]
-
A.
hasPayload
Indicates that one entity carries, contains, or is equipped with another entity as its payload.
-
B.
hasPayloadStructure
Indicates that an entity is associated with, or characterized by, a specific structure or organization of its payload.
-
C.
hasSiteCode
Indicates that an entity is associated with a specific site identifier or code used to distinguish its location or facility.
-
D.
usesPayload
Indicates that one entity employs or utilizes another entity as its payload in performing an action or function.
-
E.
containsSite
chosen
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a000fda03948190881b7275f249768f |
completed | May 10, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_6a000f607f1881908ee750d58da91690 |
completed | May 10, 2026, 4:53 a.m. |
Created at: May 3, 2026, 4:10 p.m.