Triple
T35984843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clifton C. Williams Jr. |
E1040680
|
entity |
| Predicate | wasBackupCrewMemberOf |
P50499
|
FINISHED |
| Object | Gemini 10 |
—
|
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: Gemini 10 | Statement: [Clifton C. Williams Jr., wasBackupCrewMemberOf, Gemini 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasBackupCrewMemberOf Context triple: [Clifton C. Williams Jr., wasBackupCrewMemberOf, Gemini 10]
-
A.
backupCrewAssignment
chosen
Indicates that one entity is designated to serve as a backup crew for another entity, ready to assume its duties if needed.
-
B.
wereInternedBy
Indicates that an entity was forcibly confined, detained, or held in an internment facility by another entity (typically an authority or government).
-
C.
crewInvolvedIn
Indicates that a crew (as a group or unit) participates in, contributes to, or is otherwise involved in a specified event, activity, or operation.
-
D.
crew
Indicates that one entity serves as the group of people who operate, staff, or work on another entity (such as a vehicle, vessel, or production).
-
E.
hasCrewMember
Indicates that an entity includes or employs another entity as a member of its crew.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.