Triple
T10325265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Mustang GT/CS |
E242745
|
entity |
| Predicate | generationApplicable |
P93379
|
FINISHED |
| Object | fifth-generation Ford Mustang |
—
|
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: fifth-generation Ford Mustang | Statement: [Ford Mustang GT/CS, generationApplicable, fifth-generation Ford Mustang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generationApplicable Context triple: [Ford Mustang GT/CS, generationApplicable, fifth-generation Ford Mustang]
-
A.
generationMethod
Indicates the process, technique, or procedure by which something is created, produced, or derived.
-
B.
architectureGeneration
Indicates the creation or design of an architectural structure, system, or layout from given inputs or specifications.
-
C.
generation
Indicates the relationship in which one entity produces, creates, or brings another entity into existence.
-
D.
architecturalGeneration
Indicates a relationship where one entity is responsible for creating, designing, or originating the architecture of another entity.
-
E.
generationOf
Indicates that one entity is the origin, creator, or producer of another entity.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cd76348190b93562112300acfc |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d7cada7881908beba55a1dc9ecb9 |
completed | April 7, 2026, 10:09 a.m. |
Created at: April 6, 2026, 11:51 a.m.