Triple
T35084900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Lyon |
E1012548
|
entity |
| Predicate | typeOfAccord |
P405
|
FINISHED |
| Object | peace agreement |
—
|
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: peace agreement | Statement: [Treaty of Lyon, typeOfAccord, peace agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAccord Context triple: [Treaty of Lyon, typeOfAccord, peace agreement]
-
A.
accountType
Indicates the specific category or classification of an account within a system or context.
-
B.
typeOfContract
chosen
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
C.
accessionType
Indicates the manner or category by which something is acquired, added, or admitted into a collection, system, or status.
-
D.
bankingType
Indicates the category or model of banking relationship or services associated with an entity (e.g., retail, corporate, investment).
-
E.
depositType
Indicates the specific kind or category of deposit associated with an account, transaction, or financial arrangement.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0189f3f0248190a1b018164d18e6f5 |
completed | May 11, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_6a0187ee0920819097047bb55e1f9506 |
completed | May 11, 2026, 7:40 a.m. |
Created at: May 3, 2026, 4:01 p.m.