Triple
T35476282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corfu Channel incident |
E1025341
|
entity |
| Predicate | compensationOrdered |
P191608
|
FINISHED |
| Object | £843,947 |
—
|
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: £843,947 | Statement: [Corfu Channel incident, compensationOrdered, £843,947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compensationOrdered Context triple: [Corfu Channel incident, compensationOrdered, £843,947]
-
A.
orderedProtectionBy
Indicates that one entity has formally requested or arranged protective measures to be provided by another entity.
-
B.
orderedBy
Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
-
C.
confersOrder
Indicates that one entity formally bestows or grants an order, rank, or honorific distinction upon another entity.
-
D.
joinedOrderOf
Indicates that an entity became a member of, or formally joined, a particular order or organization.
-
E.
compensationSetBy
Indicates that one party determines or establishes the compensation or pay level for another party.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.