Triple
T3676333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norrström |
E78000
|
entity |
| Predicate | relativeLength |
P50260
|
FINISHED |
| Object | short river |
—
|
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: short river | Statement: [Norrström, relativeLength, short river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeLength Context triple: [Norrström, relativeLength, short river]
-
A.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
B.
relativeLevel
Indicates a comparative relationship specifying how one entity’s level, degree, or intensity of some property stands relative to that of another entity.
-
C.
length
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
D.
proportionalTo
Indicates that one quantity varies in constant ratio to another, so changes in one are directly reflected by proportional changes in the other.
-
E.
properLengthMeasuredIn
Indicates that the proper (intrinsic or rest-frame) length of an entity is expressed using a specified unit of measurement.
- 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_69ad85e18c1c8190be8aafb227f39f48 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc462ffdc8190896e9f98f648e2f3 |
completed | March 8, 2026, 6:48 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb97cdb788190a5ce96b21bd157ab |
completed | March 8, 2026, 6:01 p.m. |
Created at: March 8, 2026, 3:25 p.m.