Triple
T27270925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expedition 63 |
E688049
|
entity |
| Predicate | commanderAffiliation |
P169561
|
FINISHED |
| Object | NASA |
—
|
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: NASA | Statement: [Expedition 63, commanderAffiliation, NASA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderAffiliation Context triple: [Expedition 63, commanderAffiliation, NASA]
-
A.
commandedUnitAllegiance
Indicates that a military or organizational unit was under the command of, and owed allegiance to, a particular leader or authority.
-
B.
typicalCrewAffiliation
Indicates the usual or standard organizational group, team, or crew with which an entity is affiliated or associated.
-
C.
commanderAlsoServesAs
Indicates that the person who holds a commander role simultaneously fulfills one or more additional official roles or positions.
-
D.
commanderNationality
Indicates the national affiliation or citizenship of a given commander.
-
E.
loreAffiliation
Indicates a relationship where an entity is associated with, belongs to, or is aligned with a particular group, faction, or organization within a fictional or narrative lore.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f67fc237608190b6542b56038a7fe4 |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 27, 2026, 10:59 a.m.