Triple
T30161726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman History (Appian) |
E766682
|
entity |
| Predicate | modernTitleVariant |
P97846
|
FINISHED |
| Object | Roman History |
—
|
NE NERFINISHED |
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: Roman History | Statement: [Roman History (Appian), modernTitleVariant, Roman History]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernTitleVariant Context triple: [Roman History (Appian), modernTitleVariant, Roman History]
-
A.
titleVariant
Indicates that one title is an alternative or variant form of another title referring to the same work or entity.
-
B.
traditionalTitleGivenBy
Indicates that one entity has conferred or assigned a traditional or customary title to another entity.
-
C.
traditionalTitle
Indicates that an entity holds or is associated with a customary or historically established title or honorific within a cultural or social tradition.
-
D.
modernVariation
Indicates that one entity is a contemporary or updated version, adaptation, or reinterpretation of another.
-
E.
modernNameForm
chosen
Indicates that one entity is the contemporary or currently used name form corresponding to another entity’s name.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 29, 2026, 7:22 p.m.