Triple
T24431244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asari |
E616005
|
entity |
| Predicate | firstSpacefaringRaceOnCitadel |
P156110
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Asari, firstSpacefaringRaceOnCitadel, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSpacefaringRaceOnCitadel Context triple: [Asari, firstSpacefaringRaceOnCitadel, true]
-
A.
firstCRSMission
Indicates that the referenced mission is the first mission conducted under the CRS (Commercial Resupply Services) program or contract.
-
B.
endedInMainColony
Indicates that an event, process, or entity concluded within the primary or central colony rather than elsewhere.
-
C.
isFirstSpacecraftTo
Indicates that a spacecraft is the earliest or initial one to reach, visit, or achieve a specified destination or milestone.
-
D.
firstCrewedDocking
Indicates the event in which a spacecraft docks with another vehicle or station with a crew on board for the first time.
-
E.
firstCrewedMission
Indicates that the mission is the first instance in which humans were onboard or directly participated as crew.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29782a4a0819087cb7ba399371520 |
completed | April 29, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:16 a.m.