Triple
T25483778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of London (1871) |
E638644
|
entity |
| Predicate | locationOfNegotiation |
P9604
|
FINISHED |
| Object | London |
—
|
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: London | Statement: [Treaty of London (1871), locationOfNegotiation, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfNegotiation Context triple: [Treaty of London (1871), locationOfNegotiation, London]
-
A.
negotiationLocation
chosen
Indicates the place or setting where a negotiation or bargaining process takes or took place.
-
B.
negotiationArea
Indicates the area or context within which negotiation between parties takes place or is intended to occur.
-
C.
positionOnNegotiations
Indicates the stance or viewpoint an entity holds regarding a particular negotiation or set of negotiations.
-
D.
negotiationAssociatedWith
Indicates a relationship where a negotiation is connected to, involves, or is conducted by a particular entity (such as a person, organization, or group).
-
E.
typeOfNegotiation
Indicates the specific kind or category of negotiation process that characterizes the interaction between the involved parties.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 21, 2026, 2:31 p.m.