Triple
T24911565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sangkum Reastr Niyum |
E623858
|
entity |
| Predicate | startTimeOfDominance |
P52387
|
FINISHED |
| Object | mid-1950s |
—
|
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: mid-1950s | Statement: [Sangkum Reastr Niyum, startTimeOfDominance, mid-1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeOfDominance Context triple: [Sangkum Reastr Niyum, startTimeOfDominance, mid-1950s]
-
A.
timePeriodOfDominance
Indicates the span of time during which an entity held dominance, control, or prevailing influence over another entity or context.
-
B.
dominatesSince
chosen
Indicates that one entity has maintained a position of dominance or control over another entity continuously from a specified starting time onward.
-
C.
startTimeAsRepresentative
Indicates the time at which an entity begins serving or acting in a representative capacity.
-
D.
startTimeAsKing
Indicates the point in time at which an individual begins their reign or role as king.
-
E.
dominantDuring
Indicates that one entity holds a prevailing or controlling influence over another specifically within a given time period or interval.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 5:28 a.m.