Triple
T1521574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Coming War on China |
E32239
|
entity |
| Predicate | productionRoleOfJohnPilger |
P15464
|
FINISHED |
| Object | director |
—
|
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: director | Statement: [The Coming War on China, productionRoleOfJohnPilger, director]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionRoleOfJohnPilger Context triple: [The Coming War on China, productionRoleOfJohnPilger, director]
-
A.
developerOfWorkAppearingIn
Indicates that one entity is the creator or developer of a work in which another entity appears or is featured.
-
B.
notableWorkRole
chosen
Indicates that a person’s role or position is specifically associated with the creation, performance, or contribution to a notable work.
-
C.
publisherRole
Indicates the specific function, capacity, or responsibility an entity has in relation to publishing a work or resource.
-
D.
journalistsFace
Indicates that journalists encounter or experience a particular challenge, condition, or situation.
-
E.
authorOccupation
Indicates the professional role or job that an author holds or is associated with.
- 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93d4756888190bf3872154de11539 |
completed | March 5, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69a907ac7ea081908dd95bb5cc3b9847 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.