Triple
T38196623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Chaumont |
E1005632
|
entity |
| Predicate | signedNearby |
P43164
|
FINISHED |
| Object | Chaumont, Haute-Marne, France |
—
|
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: Chaumont, Haute-Marne, France | Statement: [Treaty of Chaumont, signedNearby, Chaumont, Haute-Marne, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signedNearby Context triple: [Treaty of Chaumont, signedNearby, Chaumont, Haute-Marne, France]
-
A.
definedNear
Indicates that one entity is defined in close spatial or contextual proximity to another entity.
-
B.
locationSignedNear
chosen
Indicates that an entity’s location is in close physical proximity to another specified place or reference point.
-
C.
nearPass
Indicates that one entity moves or travels close to another entity without necessarily making direct contact or interaction.
-
D.
signedDuring
Indicates that an agreement, document, or contract was signed within a specified time period or during a particular event.
-
E.
placeSigned
Indicates that an entity has signed or endorsed a document, agreement, or item at a particular place or location.
- 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_69f76dbd22f48190940318cea061e8bb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:29 p.m.