Triple
T19686381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zodiac constellations |
E472720
|
entity |
| Predicate | hasTwelvefoldDivisionOf |
P1905
|
FINISHED |
| Object | ecliptic |
—
|
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: ecliptic | Statement: [Zodiac constellations, hasTwelvefoldDivisionOf, ecliptic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTwelvefoldDivisionOf Context triple: [Zodiac constellations, hasTwelvefoldDivisionOf, ecliptic]
-
A.
hasNumberOfDivisions
chosen
Indicates the relationship that specifies how many divisions or subunits an entity possesses.
-
B.
hasDivisionCounterpart
Indicates that one entity serves as the division-level equivalent or counterpart of another entity within an organizational or structural hierarchy.
-
C.
dividedIn
Indicates that one entity is partitioned or separated into multiple distinct parts, sections, or groups represented by another entity.
-
D.
hasTotalEarthlyBranches
Indicates that an entity is associated with a specific total number of Earthly Branches (e.g., in a cyclical or calendrical system).
-
E.
isDividedFrom
Indicates that one entity is separated or partitioned from another, typically by a boundary, barrier, or dividing line.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420c3f50819082b64b1fa4335e56 |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.