Triple
T38283243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belafonte |
E1022132
|
entity |
| Predicate | operatedByFictionalCharacter |
P203494
|
FINISHED |
| Object | Steve Zissou |
E312083
|
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: Steve Zissou | Statement: [Belafonte, operatedByFictionalCharacter, Steve Zissou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedByFictionalCharacter Context triple: [Belafonte, operatedByFictionalCharacter, Steve Zissou]
-
A.
operatedByFictional
chosen
Indicates that an entity (such as an organization, vehicle, or facility) is run, controlled, or managed by a fictional character or fictional organization.
-
B.
operatedByCharacter
Indicates that an operation, action, or process is carried out or controlled by a specific character.
-
C.
ownedByFictionalCharacter
Indicates that something is possessed or owned by a fictional (not real-world) character.
-
D.
managedByFictionalCharacter
Indicates that an entity is overseen, directed, or run under the authority or control of a fictional character.
-
E.
attendedByFictionalCharacter
Indicates that a fictional character is present at, participates in, or is an attendee of a particular event or gathering.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a035ac41d088190b7e76b93c1410090 |
completed | May 12, 2026, 4:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41a7dbe4b081908a61c637ab370906 |
completed | June 28, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_6a035a4f290c8190a0101295a38ae8b8 |
completed | May 12, 2026, 4:50 p.m. |
Created at: May 3, 2026, 4:30 p.m.