Triple
T35842745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matt Riddle |
E1036127
|
entity |
| Predicate | entranceAttire |
P185704
|
FINISHED |
| Object | wrestling trunks and flip-flops |
—
|
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: wrestling trunks and flip-flops | Statement: [Matt Riddle, entranceAttire, wrestling trunks and flip-flops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entranceAttire Context triple: [Matt Riddle, entranceAttire, wrestling trunks and flip-flops]
-
A.
usualAttire
Indicates the type of clothing an entity typically wears in ordinary or characteristic situations.
-
B.
hasDressCode
Indicates that a specified entity enforces or is associated with a particular set of rules governing appropriate clothing or attire.
-
C.
isFormalEntrance
Indicates that an entrance serves as the primary, officially designated point of access to a place or structure.
-
D.
ceremonialDressFeature
Indicates that one entity is a characteristic, component, or distinguishing element of another entity’s ceremonial dress or attire.
-
E.
entryOccasion
Indicates the circumstance, event, or reason that prompts or justifies an entity’s entry or initiation.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: May 3, 2026, 4:06 p.m.