Triple
T30179704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumerian calendar |
E767166
|
entity |
| Predicate | usedWithNumberSystem |
P5213
|
FINISHED |
| Object | sexagesimal system |
—
|
NE NERFINISHED |
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: sexagesimal system | Statement: [Sumerian calendar, usedWithNumberSystem, sexagesimal system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWithNumberSystem Context triple: [Sumerian calendar, usedWithNumberSystem, sexagesimal system]
-
A.
hasNumberSystem
chosen
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
-
B.
numberingSystemBasedOn
Indicates that one numbering system is derived from, structured according to, or conceptually dependent on another numbering system.
-
C.
hasUseInNumerals
Indicates that something is employed or functions as a component within numeral systems or numerical representations.
-
D.
usesPositionalNotation
Indicates that one entity represents numbers using a positional numeral system, where a digit’s value depends on its position.
-
E.
followsCountingSystemOf
Indicates that one entity uses or adheres to the same counting or numeral system as another entity.
- 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f40e2808190b08d8870702a3f5c |
completed | May 2, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:26 p.m.