Triple
T34548140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wayfarer’s Dole |
E886986
|
entity |
| Predicate | customaryContainer |
P34427
|
FINISHED |
| Object | horn cup |
—
|
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: horn cup | Statement: [Wayfarer’s Dole, customaryContainer, horn cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customaryContainer Context triple: [Wayfarer’s Dole, customaryContainer, horn cup]
-
A.
containerType
chosen
Indicates the specific kind or category of container associated with or used to hold an entity.
-
B.
containerFeature
Indicates that one entity possesses or provides a specific feature, characteristic, or capability related to a container or containment context for another entity.
-
C.
commonHolder
Indicates that two or more entities share the same holder, owner, or controlling party.
-
D.
custom
Indicates that something is specially created, configured, or tailored for a particular purpose, context, or user rather than being standard or generic.
-
E.
traditionalCustodianOf
Indicates that an entity holds recognized traditional responsibility, authority, or guardianship over another entity, often in a cultural, ancestral, or customary context.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720239d9881909ded0a06477fd9b8 |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.