Triple
T26278350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bowen’s reaction series |
E660634
|
entity |
| Predicate | continuousBranchOrder |
P165029
|
FINISHED |
| Object | Ca-rich plagioclase → Na-rich plagioclase |
—
|
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: Ca-rich plagioclase → Na-rich plagioclase | Statement: [Bowen’s reaction series, continuousBranchOrder, Ca-rich plagioclase → Na-rich plagioclase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuousBranchOrder Context triple: [Bowen’s reaction series, continuousBranchOrder, Ca-rich plagioclase → Na-rich plagioclase]
-
A.
uniformBranch
Indicates that multiple entities share the same branch, division, or organizational unit within a larger structure.
-
B.
trainedBranch
Indicates that one entity has provided training or instruction to a specific branch or subdivision of another entity.
-
C.
possibleBranch
Indicates that one entity can serve as an alternative or potential continuation path branching from another entity.
-
D.
successorBranch
Indicates that one branch directly follows or continues from another branch in a sequence or hierarchy.
-
E.
branchCount
Indicates the number of branches associated with a given entity or structure.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 26, 2026, 9:58 p.m.