Triple
T26304534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ogopogo |
E661644
|
entity |
| Predicate | reportedLength |
P161276
|
FINISHED |
| Object | 12 to 15 meters |
—
|
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: 12 to 15 meters | Statement: [Ogopogo, reportedLength, 12 to 15 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportedLength Context triple: [Ogopogo, reportedLength, 12 to 15 meters]
-
A.
usableLength
Indicates the portion of an object’s total length that can actually be used for its intended function or purpose.
-
B.
properLengthMeasuredIn
Indicates that the proper (intrinsic or rest-frame) length of an entity is expressed using a specified unit of measurement.
-
C.
estimatedOriginalLength
Indicates the approximated or inferred length that something originally had before any changes, damage, or loss.
-
D.
plannedLength
Indicates the intended or scheduled duration or size of something as determined in advance, rather than its actual or realized extent.
-
E.
surveyedLength
Indicates the measured extent or distance of something as determined through a surveying process.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 26, 2026, 10:18 p.m.