Triple
T29856304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tibetan lunar calendar |
E758196
|
entity |
| Predicate | associatesYearWith |
P207181
|
FINISHED |
| Object | animal sign |
—
|
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: animal sign | Statement: [Tibetan lunar calendar, associatesYearWith, animal sign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatesYearWith Context triple: [Tibetan lunar calendar, associatesYearWith, animal sign]
-
A.
yearAssociated
Indicates a specific year that is relevant or linked to an entity, event, or relationship (such as the year it occurred, was created, or is otherwise associated).
-
B.
associatedClassYear
Indicates a relationship linking an entity to the specific academic class year with which it is connected or identified.
-
C.
hasAssociatedYear
Indicates that an entity is linked to a specific year that is relevant to it (e.g., creation, occurrence, or reference year).
-
D.
designationYear
Indicates the year in which something was formally designated, assigned, or given an official status.
-
E.
ordinationYear
Indicates the year in which an individual was formally ordained to a religious office or role.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 5:46 p.m.