Triple
T17262903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destour |
E419049
|
entity |
| Predicate | experiencedSplitIn |
P102781
|
FINISHED |
| Object | 1934 |
—
|
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: 1934 | Statement: [Destour, experiencedSplitIn, 1934]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencedSplitIn Context triple: [Destour, experiencedSplitIn, 1934]
-
A.
commonSplit
Indicates that multiple entities share a common point or manner of division into parts.
-
B.
typicalSplit
Indicates that something is divided into parts or portions in the usual or most common way.
-
C.
separatedIn
chosen
Indicates that two or more entities, once together or associated, have been divided, split, or otherwise placed into distinct parts, groups, or locations.
-
D.
dividedIn
Indicates that one entity is partitioned or separated into multiple distinct parts, sections, or groups represented by another entity.
-
E.
experiencedProcess
Indicates that an entity has undergone or participated in a particular process or 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4379848190add32ba8e5f93527 |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.