Triple
T35974989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ben Gunn |
E1040386
|
entity |
| Predicate | formerCrewOf |
P202430
|
FINISHED |
| Object | Captain Flint |
—
|
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: Captain Flint | Statement: [Ben Gunn, formerCrewOf, Captain Flint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerCrewOf Context triple: [Ben Gunn, formerCrewOf, Captain Flint]
-
A.
crewOnboard
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
B.
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).
-
C.
carriedCrewFrom
Indicates a relationship where a vehicle or vessel transported a crew from one location or origin point to another.
-
D.
returnedCrewMember
Indicates that a person who was part of a crew has come back from a mission, trip, or assignment to a prior location or status.
-
E.
commandCrew
Indicates that one entity holds command authority over the crew associated with another entity.
- 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a007ef69f5c8190be6fb89e918d30fa |
completed | May 10, 2026, 12:49 p.m. |
| PD | Predicate disambiguation | batch_6a007e4060448190ad7420b07c1fe219 |
completed | May 10, 2026, 12:46 p.m. |
| PDg | Predicate description generation | batch_6a007ef5f05c8190a2d43e4bc45fba3f |
completed | May 10, 2026, 12:49 p.m. |
Created at: May 3, 2026, 4:07 p.m.