Triple
T17818004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Township, Michigan |
E444896
|
entity |
| Predicate | plantProduces |
P129018
|
FINISHED |
| Object | General Motors crossover SUVs |
—
|
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: General Motors crossover SUVs | Statement: [Delta Township, Michigan, plantProduces, General Motors crossover SUVs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plantProduces Context triple: [Delta Township, Michigan, plantProduces, General Motors crossover SUVs]
-
A.
plantType
Indicates the specific kind or category of plant that an entity is classified as.
-
B.
isPlantOf
Indicates that one entity is a plant that belongs to, is associated with, or is characteristic of another entity (such as a region, habitat, or owner).
-
C.
plantName
Indicates that the associated value is the name or designated label of a plant.
-
D.
growsOn
Indicates that one entity develops or increases in size, number, or extent while being physically supported by or attached to another entity.
-
E.
plant
Indicates that an entity places or sets something firmly in or on a location, often so it will grow, remain fixed, or be established there.
- F. None of above. chosen
Provenance (4 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e488812df081909771d51c54c405fe |
completed | April 19, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:14 a.m.