Triple
T31225379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MV Atlantic Conveyor |
E796120
|
entity |
| Predicate | requisitionedFor |
P54259
|
FINISHED |
| Object | Falklands War |
—
|
NE NERFINISHED |
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: Falklands War | Statement: [MV Atlantic Conveyor, requisitionedFor, Falklands War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requisitionedFor Context triple: [MV Atlantic Conveyor, requisitionedFor, Falklands War]
-
A.
requisitionedAs
Indicates that one entity has been formally requested or claimed for use as another specific resource, role, or purpose.
-
B.
requisitionedBy
chosen
Indicates that something has been formally requested or claimed for official use by a particular agent or authority.
-
C.
requisitionedDuring
Indicates that one entity was formally taken, claimed, or appropriated for use by another entity during a specified time period or event.
-
D.
shipsRequisitionedBy
Indicates that certain ships have been formally taken over or commandeered by a specified party or authority.
-
E.
requestedFor
Indicates that one entity has made a request on behalf of, or targeting, another entity as the intended recipient or subject of the request.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: April 29, 2026, 9:10 p.m.