Triple
T17846114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryūjō |
E445663
|
entity |
| Predicate | modifiedAfter |
P111413
|
FINISHED |
| Object | stability problems discovered in early service |
—
|
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: stability problems discovered in early service | Statement: [Ryūjō, modifiedAfter, stability problems discovered in early service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modifiedAfter Context triple: [Ryūjō, modifiedAfter, stability problems discovered in early service]
-
A.
changedAfter
chosen
Indicates that one entity underwent a change at a point in time that is later than the time at which another referenced entity changed.
-
B.
laterModifiedTo
Indicates that an entity was changed or updated at a later time into another specified form or state.
-
C.
modifiedDuring
Indicates that one entity underwent a change or alteration while another specified time period, process, or event was occurring.
-
D.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
E.
appliesToAfter
Indicates that one entity becomes relevant or applicable only after another specified event, condition, or time has occurred.
- 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48ffa4c648190a88a4b0733493d91 |
completed | April 19, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:16 a.m.