Triple
T18368130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Minneapolis |
E440102
|
entity |
| Predicate | navyListStatus |
P130838
|
FINISHED |
| Object | active during World War II |
—
|
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 during World War II | Statement: [USS Minneapolis, navyListStatus, active during World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navyListStatus Context triple: [USS Minneapolis, navyListStatus, active during World War II]
-
A.
NavyRegistry
Indicates a formal registration or listing of an entity within an official navy or naval organization.
-
B.
navalPowerStatus
Indicates the relative strength, capability, or strategic standing of an entity’s naval forces compared to others or to defined benchmarks.
-
C.
workStatus_OnTheCatalogueOfShips
Indicates that a work’s status is determined by whether it appears in the Catalogue of Ships section of the text.
-
D.
naveStatus
Indicates the operational or functional status currently assigned to a nave or central area within a structure.
-
E.
navalForceComposition
Indicates the makeup and distribution of different types of naval units or vessels within a particular naval force.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5174f5f448190a1fc67d3039aadd9 |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:38 a.m.