Triple
T15725656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | sexagenary cycle |
E381210
|
entity |
| Predicate | hasTotalEarthlyBranches |
P119938
|
FINISHED |
| Object | 12 |
—
|
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: 12 | Statement: [sexagenary cycle, hasTotalEarthlyBranches, 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTotalEarthlyBranches Context triple: [sexagenary cycle, hasTotalEarthlyBranches, 12]
-
A.
hasBranches
Indicates that an entity extends into multiple subordinate parts or offshoots, like limbs, divisions, or sections stemming from a main source.
-
B.
hasFamilyBranch
Indicates that one entity is a subdivision, offshoot, or branch within the broader family group or lineage of another entity.
-
C.
hasBranchOffice
Indicates that one organization maintains a branch office or subsidiary location in another place or entity.
-
D.
hasMinorityBranch
Indicates that one entity possesses or controls a branch or subsidiary in which it holds a minority (less than controlling) ownership or interest.
-
E.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
- 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_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. |
| PDg | Predicate description generation | batch_69e0094af5b481908ad51d5d7ba0c726 |
completed | April 15, 2026, 9:55 p.m. |
Created at: April 10, 2026, 4:46 a.m.