Triple
T27616208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMV |
E700443
|
entity |
| Predicate | specificationIncludes |
P5374
|
FINISHED |
| Object | card application specifications |
—
|
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: card application specifications | Statement: [EMV, specificationIncludes, card application specifications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specificationIncludes Context triple: [EMV, specificationIncludes, card application specifications]
-
A.
hasSpecification
chosen
Indicates that an entity is associated with a particular specification that defines or constrains its properties, behavior, or requirements.
-
B.
productIncludes
Indicates that a product contains, comprises, or is composed of the specified component, item, or feature.
-
C.
seriesIncludes
Indicates that a particular series contains or encompasses the referenced item as one of its constituent parts.
-
D.
componentIncluded
Indicates that one entity is a constituent part or subcomponent that is contained within or included in another entity.
-
E.
brandIncludes
Indicates that a broader brand or brand portfolio encompasses, owns, or contains the specified sub-brand, product line, or branded entity.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 2:12 p.m.