Triple
T21020221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSS Sumter |
E517784
|
entity |
| Predicate | operationalStatusAtGibraltar |
P142496
|
FINISHED |
| Object | blockaded and immobilized |
—
|
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: blockaded and immobilized | Statement: [CSS Sumter, operationalStatusAtGibraltar, blockaded and immobilized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalStatusAtGibraltar Context triple: [CSS Sumter, operationalStatusAtGibraltar, blockaded and immobilized]
-
A.
SouthamptonStatus
Indicates the status or condition of an entity specifically in relation to Southampton.
-
B.
landerStatus
Indicates the current operational or situational state of a lander in its mission lifecycle.
-
C.
hasCityGateStatus
Indicates the status or condition of a city gate in relation to a given entity.
-
D.
statusInUK
Indicates the legal or official status that an entity holds within the United Kingdom (e.g., immigration, residency, or authorization category).
-
E.
treatyStatusOfPort
Indicates the legal status of a port as defined or regulated by a specific treaty or international agreement.
- 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc5c905c8190ba2f9f82b6cd1648 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 1:54 p.m.