Triple
T14718288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oba dynasty |
E345739
|
entity |
| Predicate | encounteredEvent |
P13259
|
FINISHED |
| Object | British punitive expedition of 1897 |
—
|
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: British punitive expedition of 1897 | Statement: [Oba dynasty, encounteredEvent, British punitive expedition of 1897]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encounteredEvent Context triple: [Oba dynasty, encounteredEvent, British punitive expedition of 1897]
-
A.
observedEvent
Indicates that an entity has perceived, detected, or recorded the occurrence of a particular event.
-
B.
encountered
chosen
Indicates that one entity came across or met another entity, typically in a specific place or context, often unexpectedly or during the course of some activity.
-
C.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
D.
typicalEvent
Indicates that the associated event is a common, characteristic, or prototypical occurrence for the given entity or situation.
-
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.
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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98823408190b4b58a4c4a3fa3a3 |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.