Triple
T28829923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canal de Berry |
E728016
|
entity |
| Predicate | lockLength |
P266
|
FINISHED |
| Object | 27.5 m |
—
|
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: 27.5 m | Statement: [Canal de Berry, lockLength, 27.5 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lockLength Context triple: [Canal de Berry, lockLength, 27.5 m]
-
A.
mainLockLength
Indicates the length or extent of the primary lock mechanism involved in the relationship or action.
-
B.
inningLength
Indicates the duration or number of units (e.g., outs, minutes, or pitches) that make up a single inning in a game or sporting event.
-
C.
auxiliaryLockLength
Indicates the length or extent of an auxiliary (secondary) locking mechanism associated with an object or system.
-
D.
length
chosen
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
E.
lockType
Indicates the specific kind or category of locking mechanism or access restriction applied to an entity or resource.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6593b9f78819093476a4053ae3645 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:37 a.m.