Triple
T28751967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorguaises |
E731553
|
entity |
| Predicate | appliesToResidentsOf |
P192640
|
FINISHED |
| Object | Sorgues commune |
—
|
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: Sorgues commune | Statement: [Sorguaises, appliesToResidentsOf, Sorgues commune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToResidentsOf Context triple: [Sorguaises, appliesToResidentsOf, Sorgues commune]
-
A.
usedForResidentsOf
Indicates that something is intended to be used by, or serves the needs of, people who reside in a particular place or region.
-
B.
appliesToDistrict
Indicates that something (such as a rule, policy, or condition) is relevant or applicable to a specific district.
-
C.
hasTypicalResident
Indicates that an entity characteristically or commonly has a particular type of resident associated with it.
-
D.
effectOnNonResidents
Indicates the impact or consequences that something has on individuals who do not reside in the relevant area or jurisdiction.
-
E.
appliesToAdministrativeTerritory
Indicates that something (such as a rule, measure, or status) is valid for, relevant to, or in force within a specific administrative territory.
- F. None of above. chosen
Provenance (4 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: April 28, 2026, 6:07 a.m.