Triple
T10762208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Arkansas |
E253854
|
entity |
| Predicate | crewComplementWWI |
P95851
|
FINISHED |
| Object | about 1,063 officers and enlisted |
—
|
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: about 1,063 officers and enlisted | Statement: [USS Arkansas, crewComplementWWI, about 1,063 officers and enlisted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewComplementWWI Context triple: [USS Arkansas, crewComplementWWI, about 1,063 officers and enlisted]
-
A.
crewComplementWorldWarII
Indicates the typical number and composition of crew members assigned to operate a vessel or vehicle during World War II.
-
B.
roleInWorldWarI
Indicates the specific function, position, or involvement an entity had during World War I.
-
C.
legalStatusDuringWWI
Indicates the legal condition or classification an entity held specifically during World War I (e.g., enemy alien, neutral, ally, civilian, combatant).
-
D.
serviceBranchDuringWorldWarI
Indicates that an entity served in a specified military branch during World War I.
-
E.
commanderDuringWorldWarII
Indicates that one entity served as a commander of the other specifically during the period of World War II.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d731a230ac8190920439076aaeb91e |
completed | April 9, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa323564819097b207eb53f8a9b8 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:16 p.m.