Triple
T11399327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRH3 EMU |
E270064
|
entity |
| Predicate | manufacturingType |
P21048
|
FINISHED |
| Object | joint venture production |
—
|
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: joint venture production | Statement: [CRH3 EMU, manufacturingType, joint venture production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manufacturingType Context triple: [CRH3 EMU, manufacturingType, joint venture production]
-
A.
productionFacilityType
Indicates the specific kind or category of facility where production or manufacturing activities take place.
-
B.
typicalProductionType
Indicates the usual or characteristic type of production activity associated with an entity.
-
C.
componentTypeProduced
Indicates that one entity produces or manufactures a specific type of component as an output of its activity or process.
-
D.
equipmentTypeProduced
Indicates that an entity produces or manufactures a particular type or category of equipment.
-
E.
manufacturerType
chosen
Indicates the classification or category of a manufacturer based on its role, characteristics, or production type.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d8001adc188190ae45227856156412 |
completed | April 9, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.