Triple
T37339331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese aircraft carrier Chiyoda |
E926986
|
entity |
| Predicate | preConversionRole |
P187986
|
FINISHED |
| Object | submarine tender for midget submarines |
—
|
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: submarine tender for midget submarines | Statement: [Japanese aircraft carrier Chiyoda, preConversionRole, submarine tender for midget submarines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preConversionRole Context triple: [Japanese aircraft carrier Chiyoda, preConversionRole, submarine tender for midget submarines]
-
A.
pretrainingRole
Indicates the role or function an entity serves specifically during a pretraining phase or process.
-
B.
preConversionPractice
Indicates a practice or activity that occurs before a conversion process takes place.
-
C.
conversionRole
Indicates the specific role or function an entity plays within a conversion process or event.
-
D.
preSunRole
Indicates a role or function that an entity holds prior to assuming its role related to the sun.
-
E.
roleAfterConversion
Indicates the role or position an entity holds after undergoing a conversion, transition, or change from a previous state or role.
- 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb9e173f348190b7ab5935e4dca039 |
completed | May 6, 2026, 8:01 p.m. |
Created at: May 3, 2026, 4:16 p.m.