Triple
T26748187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RMS Lancastria |
E674459
|
entity |
| Predicate | requisitionedAs |
P181726
|
FINISHED |
| Object | troopship |
—
|
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: troopship | Statement: [RMS Lancastria, requisitionedAs, troopship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requisitionedAs Context triple: [RMS Lancastria, requisitionedAs, troopship]
-
A.
requisitionedDuring
Indicates that one entity was formally taken, claimed, or appropriated for use by another entity during a specified time period or event.
-
B.
requisitionedBy
Indicates that something has been formally requested or claimed for official use by a particular agent or authority.
-
C.
shipsRequisitionedBy
Indicates that certain ships have been formally taken over or commandeered by a specified party or authority.
-
D.
reusedIn
Indicates that something previously used in one context or instance is used again in another context or instance.
-
E.
laterRepurposedFor
Indicates that something was originally used for one purpose and subsequently assigned a different, new purpose.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: April 27, 2026, 3:52 a.m.