Triple
T1461871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Year’s Six bowls |
E31529
|
entity |
| Predicate | rotationCycleLength |
P27022
|
FINISHED |
| Object | three years |
—
|
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: three years | Statement: [New Year’s Six bowls, rotationCycleLength, three years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotationCycleLength Context triple: [New Year’s Six bowls, rotationCycleLength, three years]
-
A.
rotatesAmong
Indicates that an entity takes turns occupying or performing a role, position, or function in sequence with other entities.
-
B.
rotationType
Indicates the specific kind or mode of rotational movement or orientation applied in a given context.
-
C.
evaluationCycle
Indicates the recurring period or sequence in which evaluations or assessments are conducted and reviewed.
-
D.
hasCycleLength
chosen
Indicates that an entity participates in or exhibits a cycle whose duration or size is specified by the associated length value.
-
E.
roundCount
Indicates the number of discrete rounds or iterations that have occurred or are allocated within a process, event, or interaction.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c59ecb60819082217b034e18381f |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c48121e48190946c23c583e5fb64 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.