Triple
T18484180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Iowa (BB-4) |
E451641
|
entity |
| Predicate | laterServiceRole |
P75317
|
FINISHED |
| Object | training ship |
—
|
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: training ship | Statement: [USS Iowa (BB-4), laterServiceRole, training ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterServiceRole Context triple: [USS Iowa (BB-4), laterServiceRole, training ship]
-
A.
laterEnforcementRole
Indicates that an entity assumes or is assigned an enforcement-related role at a later time relative to another role, event, or time period.
-
B.
laterOperationalRole
chosen
Indicates that an entity assumes or is assigned a subsequent operational role after an earlier one in time.
-
C.
laterPrimaryRole
Indicates that an entity assumes a specified primary role at a later time than another role or state in a sequence.
-
D.
lambdaRole
Indicates that one entity functions as a lambda expression or anonymous functional role in relation to another entity within a logical or computational structure.
-
E.
primaryServiceRole
Indicates the main or most important functional role that a service performs in relation to other entities or processes.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d5951c81909f44362bc4101333 |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.