Triple
T25579550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAW Group |
E641201
|
entity |
| Predicate | hasMajorProductionBaseIn |
P70121
|
FINISHED |
| Object | Changchun |
—
|
NE NERFINISHED |
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: Changchun | Statement: [FAW Group, hasMajorProductionBaseIn, Changchun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorProductionBaseIn Context triple: [FAW Group, hasMajorProductionBaseIn, Changchun]
-
A.
hasMajorProductionSystem
Indicates that an entity primarily operates, utilizes, or is characterized by a particular major production system.
-
B.
hasProductionFacilitiesIn
Indicates that an entity operates or owns production facilities located within a specified geographic area or jurisdiction.
-
C.
isMajorProducerOf
Indicates that an entity plays a leading or highly significant role in producing or supplying a particular product, resource, or output.
-
D.
hasProductionBase
Indicates that one entity serves as the primary location or base where another entity’s production or manufacturing activities are carried out.
-
E.
hasPrimaryProductionLocation
chosen
Indicates that an entity’s main or principal place where it is produced or manufactured is a specified location.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 21, 2026, 4:04 p.m.