Triple
T32752576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nive de Béhérobie |
E837536
|
entity |
| Predicate | isUpperBranchOf |
P144033
|
FINISHED |
| Object | Nive |
—
|
NE NERFINISHED |
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: Nive | Statement: [Nive de Béhérobie, isUpperBranchOf, Nive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUpperBranchOf Context triple: [Nive de Béhérobie, isUpperBranchOf, Nive]
-
A.
isAnabranchOf
chosen
Indicates that one watercourse branches off from a main river or stream and later rejoins it, forming a secondary channel of the same system.
-
B.
isUniqueBranchOf
Indicates that one branch is the sole or distinct sub-branch associated with a particular parent entity or structure.
-
C.
subbranchOf
Indicates that one entity is a subordinate or secondary branch derived from, and structurally dependent on, another entity.
-
D.
isUpstreamPlantOf
Indicates that one plant facility is located or operates upstream in a process, flow, or network relative to another plant facility.
-
E.
isIndependentBranchOf
Indicates that one branch or subdivision operates autonomously and is not subordinate to the other branch or organization it is associated with.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:12 a.m.