Triple
T25177001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bingham family |
E630475
|
entity |
| Predicate | producedOccupation |
P164784
|
FINISHED |
| Object | military officers |
—
|
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: military officers | Statement: [Bingham family, producedOccupation, military officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedOccupation Context triple: [Bingham family, producedOccupation, military officers]
-
A.
workProducedBy
Indicates that a particular work (such as a creation, product, or result) was created, generated, or authored by a specific agent or entity.
-
B.
producedRole
Indicates that one entity was responsible for creating, originating, or bringing about a particular role associated with another entity.
-
C.
producedPerson
Indicates that one entity created, generated, or brought into existence the person referenced by the other entity.
-
D.
workedAsProducerFor
Indicates that one entity served in the role of producer for a work, project, or production associated with another entity.
-
E.
creatorOccupation
Indicates the professional role or job that the creator of an entity holds or held.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 21, 2026, 12:34 p.m.