Triple
T33468208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tricastini |
E857112
|
entity |
| Predicate | chiefTown |
P92693
|
FINISHED |
| Object | Augusta Tricastinorum |
—
|
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: Augusta Tricastinorum | Statement: [Tricastini, chiefTown, Augusta Tricastinorum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chiefTown Context triple: [Tricastini, chiefTown, Augusta Tricastinorum]
-
A.
principalCityOf
Indicates that a city serves as the main or most important city (often administrative, economic, or cultural center) of a specified region or area.
-
B.
mainTownOn
Indicates that one town is the primary or principal town located on or associated with a particular geographic feature, route, or area.
-
C.
primaryTown
chosen
Indicates that a given town is the main or most important town associated with an entity (such as a person, organization, or region).
-
D.
primaryCity
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
-
E.
countySeat
Indicates that one place serves as the administrative center or capital of a county.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4fb8c808190b0458e3bfe560f05 |
completed | May 3, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.