Triple
T20736381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oude Kwaremont |
E509719
|
entity |
| Predicate | hasCobbledSectionLength |
P61783
|
FINISHED |
| Object | approximately 1.6 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: approximately 1.6 kilometres | Statement: [Oude Kwaremont, hasCobbledSectionLength, approximately 1.6 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCobbledSectionLength Context triple: [Oude Kwaremont, hasCobbledSectionLength, approximately 1.6 kilometres]
-
A.
hasSectionLength
chosen
Indicates that an entity is associated with a specific length value for one of its sections.
-
B.
hasBridgeSection
Indicates that one entity includes or is associated with a specific bridge section as a distinct part or component.
-
C.
hasMinorScrambleSections
Indicates that the entity includes small or less significant sections where elements are mixed, rearranged, or scrambled.
-
D.
hasTunnelSections
Indicates that an entity includes or is composed of multiple distinct tunnel segments or portions.
-
E.
hasUndergroundLength
Indicates the extent of an object or structure that lies below ground level, measured as its underground length.
- 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_69e0b4c589c08190834fb5d86d0efa2b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c20a02d48190bba22d1bdbeb370d |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:31 p.m.