Triple
T7301970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hudson River Reserve Fleet |
E167878
|
entity |
| Predicate | functionDuringWars |
P67835
|
FINISHED |
| Object | reactivation of laid-up ships for sealift |
—
|
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: reactivation of laid-up ships for sealift | Statement: [Hudson River Reserve Fleet, functionDuringWars, reactivation of laid-up ships for sealift]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionDuringWars Context triple: [Hudson River Reserve Fleet, functionDuringWars, reactivation of laid-up ships for sealift]
-
A.
operatorDuringWar
Indicates that an entity operated or was active in its role during a time of war.
-
B.
statusDuringWar
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
C.
enemyDuringWar
Indicates that one entity is an enemy of another specifically in the context of a particular war or armed conflict.
-
D.
warPeriod
Indicates a time span during which a state of war or armed conflict is ongoing between parties.
-
E.
strategicRoleDuringWar
chosen
Indicates that an entity served a particular strategic function or importance during a specific war or armed conflict.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebb09164819099c4479d48c1688a |
completed | March 27, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.