Triple
T30161707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman History (Appian) |
E766682
|
entity |
| Predicate | historianOrigin |
P198214
|
FINISHED |
| Object | Greek |
—
|
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: Greek | Statement: [Roman History (Appian), historianOrigin, Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historianOrigin Context triple: [Roman History (Appian), historianOrigin, Greek]
-
A.
historicalOrigin
Indicates the relationship by which one entity serves as the source, origin, or starting point in history for another entity.
-
B.
historianAuthor
Indicates that one entity is the historian who authored or wrote the work represented by the other entity.
-
C.
historian
Indicates that an entity studies, interprets, or writes about past events or historical subjects in relation to another entity.
-
D.
hasHistoricalOrigin
Indicates that something originated, was first established, or came into existence during a specific historical period or context.
-
E.
historicalPeople
Indicates that the related entities are people who lived in or are associated with a past historical period or context.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69fed3569ca881909f4291baeb665d9d |
completed | May 9, 2026, 6:25 a.m. |
Created at: April 29, 2026, 7:22 p.m.