Triple
T16117794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Expo permanent markers |
E391048
|
entity |
| Predicate | capFeature |
P113792
|
FINISHED |
| Object | snap-on cap |
—
|
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: snap-on cap | Statement: [Expo permanent markers, capFeature, snap-on cap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capFeature Context triple: [Expo permanent markers, capFeature, snap-on cap]
-
A.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
B.
capSurface
Indicates that one entity serves as the top or end surface (a cap) enclosing or terminating another entity.
-
C.
hasCap
chosen
Indicates that an entity possesses or is equipped with a cap or top covering.
-
D.
maskCharacteristic
Indicates that one entity serves to conceal, obscure, or alter the apparent characteristics or properties of another entity.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2016c10a081909b2d23ecea153a9c |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.