Triple
T37419442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iulia Concordia |
E929804
|
entity |
| Predicate | modernSettlementAtSite |
P128342
|
FINISHED |
| Object | Concordia Sagittaria |
—
|
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: Concordia Sagittaria | Statement: [Iulia Concordia, modernSettlementAtSite, Concordia Sagittaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernSettlementAtSite Context triple: [Iulia Concordia, modernSettlementAtSite, Concordia Sagittaria]
-
A.
modernSettlement
chosen
Indicates that the subject is a contemporary or currently existing human settlement located at the object.
-
B.
modernArchaeologicalSite
Indicates that a location functions as an archaeological site characterized by modern-era remains, research, or excavation activities.
-
C.
modernSettlementArea
Indicates the geographic area occupied by a settlement in its modern or current form.
-
D.
modernSettlementCoreOf
Indicates that a modern settlement functions as the central or primary core area of another, broader settlement entity.
-
E.
earliestPermanentSettlement
Indicates that one entity is the location or instance of the first long-term, continuously inhabited settlement associated with another entity.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 3, 2026, 4:16 p.m.