Triple
T498008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake of Biel |
E10337
|
entity |
| Predicate | maxWidth |
P13004
|
FINISHED |
| Object | about 4.1 km |
—
|
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: about 4.1 km | Statement: [Lake of Biel, maxWidth, about 4.1 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxWidth Context triple: [Lake of Biel, maxWidth, about 4.1 km]
-
A.
hasApproximateMaximumWidth
chosen
Indicates that an entity’s maximum width is known only approximately, rather than as an exact value.
-
B.
minimumWidth
Indicates that there is a specified smallest allowable or required width for something in the relationship.
-
C.
width
Indicates the measurement of how wide an entity is, typically the extent of its horizontal dimension from side to side.
-
D.
maximumVolumeSize
Indicates the largest allowable size or capacity that a volume can have within a given system or context.
-
E.
setsMaximum
Indicates that one entity establishes an upper limit or maximum allowable value for another entity or quantity.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1183e988190bce70932a9678134 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edfa87cc8190a77c726a5a55b7d9 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.