Triple
T6561309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calendar Round |
E153787
|
entity |
| Predicate | timekeepingRole |
P15775
|
FINISHED |
| Object | short-range dating system |
—
|
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: short-range dating system | Statement: [Calendar Round, timekeepingRole, short-range dating system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timekeepingRole Context triple: [Calendar Round, timekeepingRole, short-range dating system]
-
A.
timekeepingAccuracy
Indicates how closely an entity’s measurement or tracking of time matches the true or standard reference time.
-
B.
clockType
Indicates the type or category of a clock associated with an entity (e.g., analog, digital, system clock, etc.).
-
C.
timingStandard
Indicates that one entity specifies or conforms to the timing rules, constraints, or reference schedule defined by another entity.
-
D.
timeSystem
chosen
Indicates a relationship where an entity uses, follows, or is defined within a particular system for measuring or organizing time.
-
E.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
- 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_69c6880cb35881909b763eb0125236b9 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c1b15d3481908ae66e3d7564b352 |
completed | March 27, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c6acf6d4148190914b19e9affd8c76 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:52 p.m.