Triple
T4259660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Épernay |
E96071
|
entity |
| Predicate | hasUndergroundCellarsLength |
P54999
|
FINISHED |
| Object | over 100 kilometres |
—
|
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: over 100 kilometres | Statement: [Épernay, hasUndergroundCellarsLength, over 100 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUndergroundCellarsLength Context triple: [Épernay, hasUndergroundCellarsLength, over 100 kilometres]
-
A.
hasCellars
Indicates that one entity possesses or contains one or more cellars associated with it.
-
B.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
C.
numberOfBasementLevels
Indicates the total count of basement levels associated with a given structure or property.
-
D.
hasBasement
Indicates that a building or structure includes a basement level as part of its physical layout.
-
E.
hasUndergroundMine
Indicates that one entity possesses, controls, or contains an underground mine associated with it.
- 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_69b3454095ac81909c2494f7ff294af1 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34f7fe7348190baed8d214268b756 |
completed | March 12, 2026, 11:42 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e04ef1c81908bb34ae1cbfab1e6 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:06 p.m.