Triple
T23863042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Year of the Dragon |
E592501
|
entity |
| Predicate | hasPositionInChineseZodiacCycle |
P26307
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Year of the Dragon, hasPositionInChineseZodiacCycle, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPositionInChineseZodiacCycle Context triple: [Year of the Dragon, hasPositionInChineseZodiacCycle, 5]
-
A.
hasZodiacAnimal
Indicates that one entity is associated with a particular zodiac animal in an astrological or calendrical system.
-
B.
hasZodiacSignPart
Indicates that one entity is a component, segment, or subdivision of a zodiac sign represented by the other entity.
-
C.
positionInZodiac
chosen
Indicates the specific place or rank an entity occupies within the ordered sequence of zodiac signs.
-
D.
usesSexagenaryCycleFor
Indicates that something is organized, measured, or represented using the traditional sexagenary (base-60) cyclical system.
-
E.
hasZodiacSignRange
Indicates that there is an association between an entity and a specific span of dates corresponding to a zodiac sign or set of zodiac signs.
- 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cae16df4819081a8b3a395e45118 |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:13 p.m.