Triple
T11745222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tagliamento River |
E279261
|
entity |
| Predicate | hasChannelPattern |
P8151
|
FINISHED |
| Object | braided 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: braided river | Statement: [Tagliamento River, hasChannelPattern, braided river]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChannelPattern Context triple: [Tagliamento River, hasChannelPattern, braided river]
-
A.
hasPattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
B.
hasChannel
Indicates that one entity possesses, provides, or is associated with a particular communication or distribution channel.
-
C.
hasChannelCount
Indicates that an entity is associated with a specific number of channels.
-
D.
hasCanalOrChannel
Indicates that one entity possesses, contains, or is traversed by a canal or channel that serves as a conduit or passageway.
-
E.
hasPreMessagePattern
Indicates that an entity is associated with a specific pattern or structure that must appear in a message before a given point or event.
- 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4f2a38c8190a682d8dae1ab9415 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.