Triple
T17100665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panjalu |
E414970
|
entity |
| Predicate | timeframeApproximate |
P125927
|
FINISHED |
| Object | c. 1040–1222 CE |
—
|
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: c. 1040–1222 CE | Statement: [Panjalu, timeframeApproximate, c. 1040–1222 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeframeApproximate Context triple: [Panjalu, timeframeApproximate, c. 1040–1222 CE]
-
A.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
B.
timeStartApprox
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
C.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
D.
timeframeRelative
Indicates a temporal relationship where one event, state, or condition is positioned in time relative to another (e.g., before, after, or overlapping).
-
E.
approximateAscentTime
Indicates the estimated amount of time required for an entity to ascend or climb to a specified point or elevation.
- F. None of above. chosen
Provenance (4 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc0182cc8190b8aa9c980f11ba57 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e37542d060819082aa73948eb8ebd4 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:35 a.m.