Triple
T37016679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo Command Module 012 |
E916099
|
entity |
| Predicate | crewRoleAssignment |
P16628
|
FINISHED |
| Object | Grissom – Command Pilot |
—
|
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: Grissom – Command Pilot | Statement: [Apollo Command Module 012, crewRoleAssignment, Grissom – Command Pilot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewRoleAssignment Context triple: [Apollo Command Module 012, crewRoleAssignment, Grissom – Command Pilot]
-
A.
assignsRoleTo
chosen
Indicates that one entity designates or grants a specific role or position to another entity.
-
B.
crewUser
Indicates that a user is a member of, or assigned as part of, a specific crew.
-
C.
teamAssignment
Indicates that one entity is assigned to work as part of a specific team or group.
-
D.
registryRole
Indicates the specific function or capacity an entity holds within a registry, such as how it participates in or is responsible for registry-related activities.
-
E.
roleComponent
Indicates that one entity functions as a component or constituent part within the role or capacity defined by another 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.