Triple
T16267083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Ardres |
E394902
|
entity |
| Predicate | confirmedPossessionFor |
P27902
|
FINISHED |
| Object | 8 years |
—
|
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: 8 years | Statement: [Treaty of Ardres, confirmedPossessionFor, 8 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confirmedPossessionFor Context triple: [Treaty of Ardres, confirmedPossessionFor, 8 years]
-
A.
recognizedPossession
chosen
Indicates that an entity formally acknowledges or accepts another entity’s ownership or control over something.
-
B.
confirmedFor
Indicates that an entity has been officially approved, scheduled, or validated to participate in, receive, or be associated with another specified entity or event.
-
C.
confirmedPresenceOf
Indicates that the presence or existence of an entity has been verified as true or established with certainty.
-
D.
confirmedBy
Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
-
E.
claimedFor
Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf of another entity.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c963ec8190b059fecac6248cd9 |
completed | April 17, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:05 a.m.