Triple
T31610066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VC2-M-AP4 |
E806600
|
entity |
| Predicate | designVariantCode |
P195546
|
FINISHED |
| Object | AP4 |
—
|
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: AP4 | Statement: [VC2-M-AP4, designVariantCode, AP4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designVariantCode Context triple: [VC2-M-AP4, designVariantCode, AP4]
-
A.
designVariant
Indicates that one entity is an alternative design or version derived from or related to another entity’s design.
-
B.
designCode
Indicates that one entity creates, specifies, or defines the design or coding scheme used by another entity.
-
C.
productVariant
Indicates that one entity is a specific variant or version of a more general product entity.
-
D.
exportVariantName
Indicates that one entity is the name or label of a specific variant of another entity intended for export.
-
E.
customizedVariantOf
Indicates that one entity is a modified or tailored version derived from another, preserving a core basis while introducing specific customizations.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69fdd922d73c81908ad3faade247ec16 |
completed | May 8, 2026, 12:37 p.m. |
Created at: April 30, 2026, 10:36 p.m.