Triple
T31656719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planet Express |
E807874
|
entity |
| Predicate | shipCrewMember |
P94498
|
FINISHED |
| Object | Philip J. Fry |
—
|
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: Philip J. Fry | Statement: [Planet Express, shipCrewMember, Philip J. Fry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipCrewMember Context triple: [Planet Express, shipCrewMember, Philip J. Fry]
-
A.
crewDepicted
Indicates that a particular crew or group of crew members is visually represented or shown in some form of media or depiction.
-
B.
crewMate
Indicates that two entities are members of the same crew or team, sharing a common group affiliation or working together in a joint capacity.
-
C.
coCrewMember
Indicates that two or more individuals serve together as members of the same crew on a shared mission, vehicle, or operation.
-
D.
crewOnboard
chosen
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
E.
agencyOfCrewMember
Indicates that a particular organization or agency is responsible for employing, managing, or representing the specified crew member.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:55 p.m.