Triple
T26304537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ogopogo |
E661644
|
entity |
| Predicate | reportedShape |
P1464
|
FINISHED |
| Object | long serpentine body |
—
|
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: long serpentine body | Statement: [Ogopogo, reportedShape, long serpentine body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportedShape Context triple: [Ogopogo, reportedShape, long serpentine body]
-
A.
shaped
Indicates that one entity has given form, contour, or structure to another entity or outcome.
-
B.
apparentShapeOrigin
Indicates that the perceived or apparent shape of an object is attributed to or originates from a specified source or cause.
-
C.
shapeType
Indicates the specific geometric form or category that characterizes an entity’s shape.
-
D.
shapeInfluencedBy
Indicates that the form or outline of one entity is affected, determined, or modified by another entity or factor.
-
E.
shape
chosen
Indicates that one entity has a particular geometric or physical form characterized by the other entity.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 26, 2026, 10:18 p.m.