Triple
T26529599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resilience |
E670782
|
entity |
| Predicate | crewTransportedOnCrew-1 |
P45020
|
FINISHED |
| Object | Michael S. Hopkins |
—
|
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: Michael S. Hopkins | Statement: [Resilience, crewTransportedOnCrew-1, Michael S. Hopkins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewTransportedOnCrew-1 Context triple: [Resilience, crewTransportedOnCrew-1, Michael S. Hopkins]
-
A.
carriedCrewFrom
Indicates a relationship where a vehicle or vessel transported a crew from one location or origin point to another.
-
B.
crewOnboard
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
C.
carriesCrewOf
chosen
Indicates that one entity serves as the vehicle or vessel that transports the crew belonging to another entity.
-
D.
providedCrewForMissionType
Indicates that an entity supplied or assigned crew members specifically for a particular type or category of mission.
-
E.
aboardSpacecraft
Indicates that one entity is physically present on or inside a spacecraft as an occupant or passenger.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f613f5ec28819099ec679f636d61d9 |
completed | May 2, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:34 a.m.