Triple
T34628876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bikheris |
E889215
|
entity |
| Predicate | chronologicalPlacementStatus |
P81596
|
FINISHED |
| Object | approximate and uncertain |
—
|
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: approximate and uncertain | Statement: [Bikheris, chronologicalPlacementStatus, approximate and uncertain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalPlacementStatus Context triple: [Bikheris, chronologicalPlacementStatus, approximate and uncertain]
-
A.
chronologicalStatus
chosen
Indicates the temporal state or phase of something relative to a timeline or sequence of events.
-
B.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
C.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
-
D.
chronologicRank
Indicates the relative position or order of something within a sequence based on time.
-
E.
chronologicalCriterion
Indicates a temporal condition that orders or selects entities based on when they occur or exist relative to one another.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: May 1, 2026, 2:04 a.m.