Triple
T35044221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctuaire fédéral des Trois Gaules |
E1011151
|
entity |
| Predicate | servedProvinces |
P39584
|
FINISHED |
| Object | Gallia Lugdunensis |
—
|
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: Gallia Lugdunensis | Statement: [Sanctuaire fédéral des Trois Gaules, servedProvinces, Gallia Lugdunensis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedProvinces Context triple: [Sanctuaire fédéral des Trois Gaules, servedProvinces, Gallia Lugdunensis]
-
A.
servedProvince
Indicates that an entity has provided services or held jurisdictional authority over a specified province.
-
B.
servesProvince
chosen
Indicates that one entity (typically an organization, service, or administrative unit) provides service or has jurisdiction over a specified province.
-
C.
mainProvinces
Indicates that certain provinces are the primary or most significant administrative regions associated with a given entity.
-
D.
adminProvince
Indicates that one entity serves as the administrative province or primary provincial jurisdiction for another entity.
-
E.
servesProvinceCapital
Indicates that a city functions as the administrative or service center for a given province’s capital.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffe8ebe9fc8190b1934a3c4074370c |
completed | May 10, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69ffe83a5de88190bed3e8bac86e8760 |
completed | May 10, 2026, 2:06 a.m. |
Created at: May 3, 2026, 4:01 p.m.