Triple
T23884436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Count |
E600289
|
entity |
| Predicate | includesTimeUnit |
P18870
|
FINISHED |
| Object | kʼin |
—
|
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: kʼin | Statement: [Long Count, includesTimeUnit, kʼin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTimeUnit Context triple: [Long Count, includesTimeUnit, kʼin]
-
A.
hasTimeComponent
Indicates that something includes, is associated with, or is characterized by a specific temporal aspect or time-related element.
-
B.
timeSpanIncludes
Indicates that one time span fully contains or covers the entire duration of another time span.
-
C.
timeScaleUnit
chosen
Indicates the unit of temporal measurement (such as seconds, minutes, or hours) used to express a given time scale.
-
D.
hasTimeOptions
Indicates that an entity is associated with one or more selectable time choices or configurations.
-
E.
hasTimeIndication
Indicates that something includes, specifies, or is associated with a particular time-related indication (such as a timestamp, time period, or temporal marker).
- 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_69e295318e148190b9979d8fc02e168f |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ccfbbe4c819093e590709719ab72 |
completed | April 29, 2026, 9:18 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:24 p.m.