Triple
T29682565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bullis |
E750994
|
entity |
| Predicate | relatedToModelGeneration |
P97305
|
FINISHED |
| Object | Volkswagen Type 2 T1 |
—
|
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: Volkswagen Type 2 T1 | Statement: [Bullis, relatedToModelGeneration, Volkswagen Type 2 T1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToModelGeneration Context triple: [Bullis, relatedToModelGeneration, Volkswagen Type 2 T1]
-
A.
associatedModelGeneration
Indicates that one entity is responsible for creating, producing, or generating another related model or representation.
-
B.
secondGenerationRelatedModel
Indicates that one model is derived from or based on another model that is itself already a derived (first-generation) model, forming a second-generation relationship.
-
C.
belongsToGeneration
Indicates that an entity is associated with, classified within, or a member of a particular generation or generational group.
-
D.
associatedWithModel
chosen
Indicates that one entity has a defined connection, linkage, or relationship with a particular model.
-
E.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a0191d96dc88190ac0823e534f9d704 |
completed | May 11, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_6a01908110448190a46442ffe4d15f5f |
completed | May 11, 2026, 8:17 a.m. |
Created at: April 28, 2026, 7:11 p.m.