Triple
T35261125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bread and Circuses |
E1018371
|
entity |
| Predicate | featuresShipCrew |
P94498
|
FINISHED |
| Object | crew of the USS Enterprise (NCC-1701) |
E327462
|
NE FINISHED |
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: crew of the USS Enterprise (NCC-1701) | Statement: [Bread and Circuses, featuresShipCrew, crew of the USS Enterprise (NCC-1701)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresShipCrew Context triple: [Bread and Circuses, featuresShipCrew, crew of the USS Enterprise (NCC-1701)]
-
A.
featureCrew
Indicates that a particular crew member is highlighted or designated as a featured participant within a crew-related context.
-
B.
crewCount
Indicates the number of crew members associated with an entity, such as a vehicle, vessel, or mission.
-
C.
intendedCrew
Indicates that an entity is designated or planned to serve as the crew for another entity (such as a vehicle, mission, or operation).
-
D.
crewOnboard
chosen
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
E.
crewCountApproximate
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
- F. None of above.
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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a380fb62da08190b83e4e5a65b33f19 |
completed | June 21, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.