Triple
T24071493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | canton of Nîmes-1 |
E596242
|
entity |
| Predicate | partiallyCovers |
P16474
|
FINISHED |
| Object | commune of Nîmes |
—
|
LITERAL FINISHED |
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: commune of Nîmes | Statement: [canton of Nîmes-1, partiallyCovers, commune of Nîmes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyCovers Context triple: [canton of Nîmes-1, partiallyCovers, commune of Nîmes]
-
A.
partlyCoveredBy
chosen
Indicates that one entity is covered or overlapped by another entity, but only to a partial extent rather than completely.
-
B.
isCoveredIn
Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
-
C.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
-
D.
doubleCoveredBy
Indicates that an entity is fully covered or overlapped twice by another entity or pair of entities, such that it is included in two distinct covering relationships.
-
E.
isCoveredBy
Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db191d288190af438be742e02252 |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:41 p.m.