Triple
T24237143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Abernethy (1072) |
E601915
|
entity |
| Predicate | placeOfAgreement |
P8839
|
FINISHED |
| Object | Abernethy |
—
|
NE NERFINISHED |
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: Abernethy | Statement: [Treaty of Abernethy (1072), placeOfAgreement, Abernethy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfAgreement Context triple: [Treaty of Abernethy (1072), placeOfAgreement, Abernethy]
-
A.
negotiationLocation
Indicates the place or setting where a negotiation or bargaining process takes or took place.
-
B.
treatySignedPlace
chosen
Indicates the location where a treaty was formally signed or concluded.
-
C.
formedByAgreementWith
Indicates that something comes into existence or is established as a direct result of a formal agreement between parties.
-
D.
agreement
Indicates that two or more parties mutually consent to and accept shared terms, conditions, or understandings.
-
E.
aimOfAgreement
Indicates the intended purpose or objective that an agreement is designed to achieve.
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f28a9c5c3081909cfddc8d29121817 |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:02 a.m.