Triple
T38209035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slidell Mission to Mexico |
E1009286
|
entity |
| Predicate | diplomaticAgent |
P2921
|
FINISHED |
| Object | John Slidell |
E308351
|
NE 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: John Slidell | Statement: [Slidell Mission to Mexico, diplomaticAgent, John Slidell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diplomaticAgent Context triple: [Slidell Mission to Mexico, diplomaticAgent, John Slidell]
-
A.
diplomaticInstrumentFor
Indicates a relationship where something is used as a means or tool to conduct or achieve diplomatic relations or objectives between parties.
-
B.
diplomaticRole
chosen
Indicates that an entity holds or has held an official diplomatic position or function in relation to another entity or context.
-
C.
diplomaticTool
Indicates the use of an object, method, or channel as a means or instrument for conducting diplomatic relations or negotiations between parties.
-
D.
typeOfDiplomaticRole
Indicates the specific kind or category of diplomatic position or function that an entity holds in relation to another.
-
E.
signatoryDiplomat
Indicates that a diplomat is an official signatory to an agreement, treaty, or formal document.
- F. None of above.
Provenance (4 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_69f76dc94fcc8190bd2f55e81f9d6527 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a418545089c81909ffcbc61a600aed0 |
completed | June 28, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.