Triple
T19251388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hipponion |
E481400
|
entity |
| Predicate | underRomanControl |
P22322
|
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: [Hipponion, underRomanControl, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underRomanControl Context triple: [Hipponion, underRomanControl, true]
-
A.
underRomanRule
chosen
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
-
B.
statusAfterRomanConquest
Indicates the condition or standing of an entity following its conquest by the Roman state or Roman forces.
-
C.
underRomanRuleBecame
Indicates that an entity, once under Roman political or administrative control, subsequently transformed into or was reconstituted as another specified entity.
-
D.
eraOfRomanConquest
Indicates the historical period during which the Roman Empire conquered or brought the referenced entity under Roman control.
-
E.
wasRomanProtectorate
Indicates that one political entity was under the protection and partial control of the Roman state as a protectorate.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb30bf6c819094c44aceb544a023 |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:27 p.m.