Triple
T24911632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sangkum |
E623859
|
entity |
| Predicate | significantEventDuringRule |
P157867
|
FINISHED |
| Object | construction of Sihanoukville |
—
|
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: construction of Sihanoukville | Statement: [Sangkum, significantEventDuringRule, construction of Sihanoukville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantEventDuringRule Context triple: [Sangkum, significantEventDuringRule, construction of Sihanoukville]
-
A.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
B.
significantEventType
Indicates the specific category or kind of major or noteworthy event associated with an entity or situation.
-
C.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
-
D.
significantEventContext
Indicates that an event occurs within a context or circumstances that are particularly important, influential, or meaningful relative to that event.
-
E.
significantConcurrentEvent
Indicates that another event occurs at the same time and is of notable or meaningful importance in relation to the referenced event.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 5:28 a.m.