Triple
T5706665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Club C |
E125799
|
entity |
| Predicate | soleType |
P65694
|
FINISHED |
| Object | rubber cupsole |
—
|
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: rubber cupsole | Statement: [Club C, soleType, rubber cupsole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soleType Context triple: [Club C, soleType, rubber cupsole]
-
A.
footType
Indicates the specific kind or classification of feet that an entity possesses or is characterized by.
-
B.
traditionalFootwear
Indicates that the relationship involves footwear that is characteristic of, or historically associated with, a particular culture, region, or tradition.
-
C.
earType
Indicates the specific kind or classification of ears associated with an entity.
-
D.
singleType
Indicates that an entity belongs to exactly one specific type or category, with no additional types assigned.
-
E.
slipType
Indicates the specific category or kind of slip involved in an action or relationship between entities.
- 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_69c0082d6fe48190b777fb383769e5c8 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0248751bc8190b12aaa42d1ef17e3 |
completed | March 22, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69c021c2d8bc8190b947c7d1f423d2f3 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c023dfec6881909ee6189b874b4348 |
completed | March 22, 2026, 5:16 p.m. |
Created at: March 22, 2026, 3:45 p.m.