Triple
T24431804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Normandy SR-1 crew |
E616016
|
entity |
| Predicate | notableHumanMembers |
P139960
|
FINISHED |
| Object | Commander Shepard |
—
|
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: Commander Shepard | Statement: [Normandy SR-1 crew, notableHumanMembers, Commander Shepard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHumanMembers Context triple: [Normandy SR-1 crew, notableHumanMembers, Commander Shepard]
-
A.
notablePersonnel
Indicates that the subject has associated individuals who are particularly important, distinguished, or prominent in relation to it.
-
B.
notableMemberWorld
Indicates that an entity is a particularly prominent or distinguished member within a global or worldwide group, organization, or context.
-
C.
notableHuman
chosen
Indicates that the subject is a human who is recognized as notable or significant in some context.
-
D.
hasNotableMember
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
-
E.
notableFemaleMember
Indicates that an entity has a female member who is particularly prominent, distinguished, or noteworthy within that entity.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29783b3208190997c47be1aa229af |
completed | April 29, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:16 a.m.