Triple
T4228180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antiochus IV Epiphanes |
E94510
|
entity |
| Predicate | selfRepresentation |
P4296
|
FINISHED |
| Object | divine king |
—
|
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: divine king | Statement: [Antiochus IV Epiphanes, selfRepresentation, divine king]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selfRepresentation Context triple: [Antiochus IV Epiphanes, selfRepresentation, divine king]
-
A.
selfIdentification
chosen
Indicates that an entity defines or declares its own identity, attributes, or classification about itself.
-
B.
selfListing
Indicates that an entity is listing, advertising, or registering itself rather than being listed by another party.
-
C.
representation
Indicates that one entity stands in for, symbolizes, or depicts another entity in some context.
-
D.
formerRepresentation
Indicates that one entity previously served as the representative (e.g., legal, political, or organizational) of another entity, but no longer holds that role.
-
E.
representedTo
Indicates that one entity formally acted on behalf of or served as the representative of another entity in a given context or interaction.
- 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e51817c8190bff50f2c3b5deea0 |
completed | March 12, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69b347f1d7b48190bd8974c03c7dc937 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.