Triple
T3329503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Dahomey |
E69998
|
entity |
| Predicate | timelineNote |
P34213
|
FINISHED |
| Object | fell to French colonial conquest in 1894 |
—
|
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: fell to French colonial conquest in 1894 | Statement: [Kingdom of Dahomey, timelineNote, fell to French colonial conquest in 1894]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timelineNote Context triple: [Kingdom of Dahomey, timelineNote, fell to French colonial conquest in 1894]
-
A.
chronologyNote
chosen
Indicates a note that explains or clarifies the temporal order, dating, or sequence of related events or records.
-
B.
chronologicalRangeOfNotes
Indicates the time span or period covered by the associated notes in chronological order.
-
C.
navigationNote
Indicates that there is an auxiliary note or instruction intended to guide or assist navigation within a resource, interface, or environment.
-
D.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
E.
dateNote
Indicates a note, comment, or annotation that is specifically associated with a particular date or dating information.
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb171ee0881908642504ab0ac8329 |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.