Triple
T24781609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qart Hadasht |
E620008
|
entity |
| Predicate | regionControlledFrom |
P100363
|
FINISHED |
| Object | Carthaginian Iberia |
—
|
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: Carthaginian Iberia | Statement: [Qart Hadasht, regionControlledFrom, Carthaginian Iberia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionControlledFrom Context triple: [Qart Hadasht, regionControlledFrom, Carthaginian Iberia]
-
A.
rangeControlledBy
Indicates that the extent or scope of something is regulated, limited, or determined by another entity.
-
B.
townControlled
Indicates that one entity has governing authority or administrative control over a town.
-
C.
regionFrom
chosen
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
-
D.
controlsRegion
Indicates that one entity has authoritative power or governing influence over a specified geographic or administrative region.
-
E.
isControlledUnder
Indicates that one entity is subject to regulatory, legal, or authoritative control exercised by another entity or governing framework.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 4:44 a.m.