Triple
T8810112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Aviation Cadet Program |
E209635
|
entity |
| Predicate | producedRole |
P84724
|
FINISHED |
| Object | naval aviator |
—
|
LITERAL 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: naval aviator | Statement: [Naval Aviation Cadet Program, producedRole, naval aviator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedRole Context triple: [Naval Aviation Cadet Program, producedRole, naval aviator]
-
A.
playedRoleIn
Indicates that an entity performed or assumed a specific role or character within a particular event, production, or context.
-
B.
notableWorkRole
Indicates that a person’s role or position is specifically associated with the creation, performance, or contribution to a notable work.
-
C.
producedPerson
Indicates that one entity created, generated, or brought into existence the person referenced by the other entity.
-
D.
producerRole
Indicates that an entity serves in the role of producer for another entity, such as a work, product, or event.
-
E.
producedFilm
Indicates that one entity served as the producer (or production company) responsible for making or financing the creation of a particular film.
- 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fd69df4819091e9a7dad87265a4 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1f28ec8190a34311cb412920c2 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:45 p.m.