Triple
T21716805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Redfin (SS-272) |
E536050
|
entity |
| Predicate | serviceStatusDuringWWII |
P19660
|
FINISHED |
| Object | active |
—
|
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: active | Statement: [USS Redfin (SS-272), serviceStatusDuringWWII, active]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceStatusDuringWWII Context triple: [USS Redfin (SS-272), serviceStatusDuringWWII, active]
-
A.
statusDuringWorldWarII
chosen
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
-
B.
legalStatusDuringWWI
Indicates the legal condition or classification an entity held specifically during World War I (e.g., enemy alien, neutral, ally, civilian, combatant).
-
C.
serviceBranchDuringWorldWarII
Indicates that an entity served in a specified branch of the military during World War II.
-
D.
serviceBranchDuringWorldWarI
Indicates that an entity served in a specified military branch during World War I.
-
E.
operatorDuringWorldWarII
Indicates that an entity operated or was active in its role during the period of World War II.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd96ab4c88190b76f4a6b7c855039 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.