Triple
T32925065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mulk |
E842246
|
entity |
| Predicate | timeSystemContext |
P15775
|
FINISHED |
| Object | Badíʻ calendar structure of 19 months of 19 days |
—
|
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: Badíʻ calendar structure of 19 months of 19 days | Statement: [Mulk, timeSystemContext, Badíʻ calendar structure of 19 months of 19 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeSystemContext Context triple: [Mulk, timeSystemContext, Badíʻ calendar structure of 19 months of 19 days]
-
A.
timeSystem
chosen
Indicates a relationship where an entity uses, follows, or is defined within a particular system for measuring or organizing time.
-
B.
timeZoneContext
Indicates the time zone setting or context in which an event, action, or relationship is interpreted.
-
C.
timeDomain
Indicates that something is characterized, defined, or analyzed with respect to time rather than another domain (such as frequency or space).
-
D.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
-
E.
timeDomainComponent
Indicates that one entity is a component or segment of another entity within the time domain, such as a specific time interval or temporal part of a larger temporal whole.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:20 a.m.