Triple
T10008682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fake Empire |
E198314
|
entity |
| Predicate | hasPoliticalSubtext |
P46502
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Fake Empire, hasPoliticalSubtext, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliticalSubtext Context triple: [Fake Empire, hasPoliticalSubtext, true]
-
A.
politicalMeaning
chosen
Indicates that one entity expresses, embodies, or conveys a political significance, interpretation, or implication in relation to another entity.
-
B.
hasPoliticalDialogue
Indicates that there is an exchange or interaction between entities involving political topics, issues, or negotiations.
-
C.
politicallySensitive
Indicates that an entity, action, or topic is associated with political issues, controversies, or power structures such that it may require special caution, regulation, or discretion.
-
D.
hasPoliticalCharacteristic
Indicates that an entity possesses a specific political attribute, quality, or affiliation.
-
E.
hasDebatedMeaning
Indicates that the meaning or interpretation of something is contested, disputed, or subject to ongoing debate.
- 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_69ca830fcca48190bbbd9b20c233835f |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd38659c8190830d223edbfd74ec |
completed | April 2, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69cd1da2cf9081908a6c0eb5247d0bc2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:52 p.m.