Triple
T3625998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 50th Space Wing |
E76839
|
entity |
| Predicate | dateRedesignatedAsSpaceWing |
P49618
|
FINISHED |
| Object | 1985-01-30 |
—
|
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: 1985-01-30 | Statement: [50th Space Wing, dateRedesignatedAsSpaceWing, 1985-01-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateRedesignatedAsSpaceWing Context triple: [50th Space Wing, dateRedesignatedAsSpaceWing, 1985-01-30]
-
A.
designationDateAsSpaceport
Indicates the date on which a location was officially designated or recognized as a spaceport.
-
B.
missionPatchDesigner
Indicates that one entity is the designer or creator of the mission patch associated with another entity (typically a space mission).
-
C.
starshipRegistry
Indicates a formal registration relationship where a starship is recorded in an official registry or database.
-
D.
servicedSpacecraft
Indicates that one entity has performed maintenance or support operations on a spacecraft.
-
E.
orbiterDesignation
Indicates that one entity is designated as an orbiter (spacecraft or object in orbit) associated with another entity.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2dae7a48190809d4455b2349aaa |
completed | March 8, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb902e61c81908f10494f828e260f |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:23 p.m.