Triple
T15725649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sexagenary cycle |
E381210
|
entity |
| Predicate | hasOrderingRule |
P2846
|
FINISHED |
| Object | pairing stems and branches sequentially |
—
|
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: pairing stems and branches sequentially | Statement: [sexagenary cycle, hasOrderingRule, pairing stems and branches sequentially]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrderingRule Context triple: [sexagenary cycle, hasOrderingRule, pairing stems and branches sequentially]
-
A.
hasOrderingMethod
Indicates that there is a specific method or procedure used to place or arrange an order for something.
-
B.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
C.
hasRule
chosen
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
D.
hasRuleOver
Indicates that one entity holds authority, control, or governance over another entity.
-
E.
hasRankOrder
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb357a88190a92641c8a8c20573 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.