Triple
T32424867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honda Suzuka factory |
E828549
|
entity |
| Predicate | hasWorkShiftSystem |
P11916
|
FINISHED |
| Object | shift-based manufacturing operations |
—
|
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: shift-based manufacturing operations | Statement: [Honda Suzuka factory, hasWorkShiftSystem, shift-based manufacturing operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkShiftSystem Context triple: [Honda Suzuka factory, hasWorkShiftSystem, shift-based manufacturing operations]
-
A.
hasWorkSchedule
Indicates that an entity is assigned or follows a specific work schedule, defining when they are expected to work.
-
B.
hasNumberOfShifts
chosen
Indicates the quantity of work shifts associated with a given entity.
-
C.
hasDynamicShifts
Indicates that something exhibits changes or transitions in state, intensity, or behavior over time rather than remaining constant.
-
D.
hasWorkClassificationSystem
Indicates that an entity is associated with a particular system used to classify or organize types of work.
-
E.
hasWorkPeriod
Indicates that an entity is associated with a specific span of time during which it performs or is engaged in some work or activity.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 1, 2026, 12:54 a.m.