Triple
T15582509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplementary Agreement of 1905–1906 |
E374534
|
entity |
| Predicate | signedInPeriod |
P4326
|
FINISHED |
| Object | 1905–1906 |
—
|
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: 1905–1906 | Statement: [Supplementary Agreement of 1905–1906, signedInPeriod, 1905–1906]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedInPeriod Context triple: [Supplementary Agreement of 1905–1906, signedInPeriod, 1905–1906]
-
A.
signedDuring
chosen
Indicates that an agreement, document, or contract was signed within a specified time period or during a particular event.
-
B.
signOnDate
Indicates the date on which an entity formally signs or enters into an agreement, contract, or system.
-
C.
registrationPeriod
Indicates the time span during which registration for something is open or valid.
-
D.
establishedPeriod
Indicates the time span or date range during which something was founded, created, or formally brought into existence.
-
E.
signedBetween
Indicates that a formal agreement or document has been signed involving two or more parties as participants in that signing.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e45ee3c8190a6aee06a5805ca39 |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:11 a.m.