Triple
T21479932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franco-Scottish relations |
E529960
|
entity |
| Predicate | hasDiplomaticDimension |
P144515
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Franco-Scottish relations, hasDiplomaticDimension, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiplomaticDimension Context triple: [Franco-Scottish relations, hasDiplomaticDimension, yes]
-
A.
hasDiplomaticLevel
Indicates the degree or status of formal diplomatic relations that exists between two entities.
-
B.
hasDiplomaticForm
Indicates that an entity maintains a specific type or mode of diplomatic representation or relations.
-
C.
hasDiplomaticAction
Indicates that one entity performs, initiates, or is involved in a formal diplomatic action or engagement directed toward another entity.
-
D.
diplomaticSignificance
Indicates the importance or impact that an event, action, or entity has within diplomatic relations between parties or states.
-
E.
hasDiplomaticTheme
Indicates that something involves or centers on diplomatic relations, negotiations, or international political interactions.
- F. None of above. chosen
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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea1b0130819088b8e96ddbb29317 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:20 p.m.