Triple
T34375202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attalia |
E882266
|
entity |
| Predicate | inAncientProvince |
P86358
|
FINISHED |
| Object | Roman province of Pamphylia |
—
|
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 province of Pamphylia | Statement: [Attalia, inAncientProvince, Roman province of Pamphylia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inAncientProvince Context triple: [Attalia, inAncientProvince, Roman province of Pamphylia]
-
A.
provinceInAntiquity
chosen
Indicates that an entity functioned as a province or provincial territory during an ancient or classical historical period.
-
B.
ancientDistrictOf
Indicates that one entity is an ancient or historical district that forms part of, or is located within, another entity.
-
C.
ancientStates
Indicates that the related entity functioned as a state or political entity in ancient times.
-
D.
ancientCity
Indicates that the subject is a historically old or long-established city, typically originating from ancient times.
-
E.
hasAncientCityState
Indicates that one entity possesses, contains, or is associated with an ancient city-state as part of its historical or geographical context.
- 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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.