Triple
T25716431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Co-Principality of Andorra |
E644874
|
entity |
| Predicate | defenceResponsibilitySharedWith |
P56398
|
FINISHED |
| Object | France |
E861
|
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: France | Statement: [Co-Principality of Andorra, defenceResponsibilitySharedWith, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenceResponsibilitySharedWith Context triple: [Co-Principality of Andorra, defenceResponsibilitySharedWith, France]
-
A.
defensiveResponsibility
Indicates that one entity bears responsibility for protecting, guarding, or defending another entity or asset.
-
B.
hasResponsibilitiesSharedWith
chosen
Indicates that two or more entities share joint responsibility for certain tasks, duties, or obligations.
-
C.
defenceHandledBy
Indicates that responsibility for managing or conducting a defence is assigned to or carried out by a particular agent or entity.
-
D.
defencePartner
Indicates a relationship where one entity collaborates with or supports another in matters of defense or security.
-
E.
airDefenseResponsibility
Indicates that an entity has the duty or authority to protect a specified area, asset, or force against airborne threats.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10d9ff3df4819099b40aaf43cf83b6 |
completed | May 22, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 21, 2026, 9:43 p.m.