Triple
T5275045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Javanese calendar |
E119352
|
entity |
| Predicate | timeReckoning |
P15775
|
FINISHED |
| Object | lunisolar |
—
|
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: lunisolar | Statement: [Javanese calendar, timeReckoning, lunisolar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeReckoning Context triple: [Javanese calendar, timeReckoning, lunisolar]
-
A.
timeBehind
Indicates that one entity occurs or is positioned later in time than another, lagging behind it on a temporal scale.
-
B.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
C.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
D.
timeEquivalentOf
Indicates that two temporal entities represent the same point in time or duration, possibly expressed in different formats or units.
-
E.
timeSystem
chosen
Indicates a relationship where an entity uses, follows, or is defined within a particular system for measuring or organizing time.
- 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_69bd446c38e081908cdaf113bdf86790 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7c23bed88190b406dee21957d823 |
completed | March 20, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69bd77c83d1c8190bd8b9616113d413c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.