Triple
T10248104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Ishikawajima Shipbuilding and Engineering |
E240270
|
entity |
| Predicate | laterBusiness |
P44322
|
FINISHED |
| Object | automotive manufacturing |
—
|
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: automotive manufacturing | Statement: [Tokyo Ishikawajima Shipbuilding and Engineering, laterBusiness, automotive manufacturing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterBusiness Context triple: [Tokyo Ishikawajima Shipbuilding and Engineering, laterBusiness, automotive manufacturing]
-
A.
laterBusinessBase
Indicates that one business entity serves as the subsequent or successor base of operations relative to another business entity.
-
B.
laterMainBusiness
chosen
Indicates that one business activity or enterprise occurs after and succeeds another as the main business.
-
C.
laterWork
Indicates that one work was created, published, or produced after another work in time.
-
D.
laterOffice
Indicates that one office or term of office occurs chronologically after another office or term.
-
E.
laterWorkBy
Indicates that one work was created after another work by the same creator or author.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d328272c8190a3548d7f7f38cfc4 |
completed | April 7, 2026, 9:49 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ebd6c88190a1f3f4a72a99d6fe |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:27 a.m.