Triple
T32150888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassinga raid |
E821154
|
entity |
| Predicate | opponentClaim |
P38117
|
FINISHED |
| Object | camp was mainly a refugee camp |
—
|
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: camp was mainly a refugee camp | Statement: [Cassinga raid, opponentClaim, camp was mainly a refugee camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentClaim Context triple: [Cassinga raid, opponentClaim, camp was mainly a refugee camp]
-
A.
opponentInCase
Indicates that two parties are on opposing sides in the same legal case or proceeding.
-
B.
challengesClaim
Indicates that one entity disputes, questions, or opposes the validity or correctness of another entity’s claim.
-
C.
alsoClaimedBy
Indicates that the same item, statement, or resource is asserted or claimed by an additional party besides the primary one.
-
D.
dissentClaimed
Indicates that an entity has expressed disagreement or opposition to a claim made by another entity.
-
E.
allegedByOpponents
chosen
Indicates that a claim or accusation is made by opponents of the subject.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:31 a.m.