Triple
T24997235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schleswig plebiscites |
E625604
|
entity |
| Predicate | resultImplementedOn |
P160085
|
FINISHED |
| Object | 1920-06-15 |
—
|
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: 1920-06-15 | Statement: [Schleswig plebiscites, resultImplementedOn, 1920-06-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultImplementedOn Context triple: [Schleswig plebiscites, resultImplementedOn, 1920-06-15]
-
A.
implementedOn
Indicates that something (such as a feature, standard, or specification) is realized, executed, or put into effect within or on a particular platform, system, or environment.
-
B.
areImplementedBy
Indicates that one entity serves as the concrete realization or execution of the specification, design, or interface defined by another entity.
-
C.
implementedFor
Indicates that one entity has been created, developed, or configured to operate on behalf of, or to fulfill the needs or requirements of, another entity.
-
D.
currentlyImplementedBy
Indicates that a given specification, design, or feature is presently realized or supported by a particular implementation or system.
-
E.
commonlyImplementedBy
Indicates that the referenced item (e.g., a standard, interface, or pattern) is frequently realized or put into practice by the associated implementing entities.
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6018f91248190985323d1a678e539 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 18, 2026, 6:04 a.m.