Triple
T23798313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wuling Motors |
E588597
|
entity |
| Predicate | notableModelCategory |
P74159
|
FINISHED |
| Object | microvans |
—
|
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: microvans | Statement: [Wuling Motors, notableModelCategory, microvans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableModelCategory Context triple: [Wuling Motors, notableModelCategory, microvans]
-
A.
notableModel
Indicates that an entity is a particularly important, influential, or exemplary instance or version within a broader category or system.
-
B.
notableCategoryType
chosen
Indicates that an entity is notably associated with or classified under a particular category type.
-
C.
notableCategory
Indicates that an entity is recognized as notable or significant within a particular category or classification.
-
D.
notableTypeOf
Indicates that one entity is a particularly prominent, well-known, or exemplary instance or subtype of another entity.
-
E.
notableClientCategory
Indicates that an entity is recognized for serving or being associated with clients belonging to a particular notable category or segment.
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6dea2888190b3ff1c96da5cfefb |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:51 p.m.