Triple
T26434042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lennox Island |
E664590
|
entity |
| Predicate | conflictResolutionMethod |
P6659
|
FINISHED |
| Object | papal mediation |
—
|
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: papal mediation | Statement: [Lennox Island, conflictResolutionMethod, papal mediation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictResolutionMethod Context triple: [Lennox Island, conflictResolutionMethod, papal mediation]
-
A.
conflictResolvedBy
Indicates that a conflict or dispute is settled or addressed through the actions, decisions, or intervention of a specified entity or process.
-
B.
resolutionMethod
Indicates the specific approach, technique, or process used to resolve a problem, conflict, or issue.
-
C.
conflictManagementMechanism
Indicates a relationship where a method, process, or system is used to prevent, manage, or resolve conflicts between parties or interests.
-
D.
methodOfDisputeResolution
chosen
Indicates the process or mechanism used to settle a disagreement or conflict between parties.
-
E.
basedOnConflict
Indicates that one entity is derived from, influenced by, or structured around a particular conflict involving another entity.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6247480cc8190a887eedaeb94615c |
completed | May 2, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69f623a7539c8190b71797f583da9f63 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 26, 2026, 11:52 p.m.