Triple
T25117355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mattole River |
E629164
|
entity |
| Predicate | freeFlowing |
P157661
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mattole River, freeFlowing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freeFlowing Context triple: [Mattole River, freeFlowing, true]
-
A.
freelyFloating
Indicates that an entity is not fixed or attached to anything and can move or remain suspended without constraint in a surrounding medium.
-
B.
freeFloatRequirement
Indicates that there is a specified minimum proportion of a security’s shares that must be freely tradable (not closely held) in the market.
-
C.
freedBy
Indicates that an entity is released or liberated as a result of an action performed by another entity.
-
D.
freeFrom
Indicates that one entity does not contain, is not affected by, or is exempt from another specified entity, condition, or constraint.
-
E.
freeFloatAdjustment
Indicates an adjustment made to account for the portion of shares that are freely tradable (free float), typically modifying a value or metric based on the free-float share base.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f465c88e888190a39cb4c5ec776b8e |
completed | May 1, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:27 a.m.