Triple
T26438743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walt Frazier |
E665025
|
entity |
| Predicate | styleOffCourt |
P160755
|
FINISHED |
| Object | flamboyant outfits |
—
|
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: flamboyant outfits | Statement: [Walt Frazier, styleOffCourt, flamboyant outfits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleOffCourt Context triple: [Walt Frazier, styleOffCourt, flamboyant outfits]
-
A.
styleOffCourt
chosen
Indicates a relationship where an entity’s fashion, behavior, or persona is characterized specifically outside the formal or professional setting associated with their main role (e.g., off the court, field, or stage).
-
B.
styleOfPlay
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
C.
hasCourtSurface
Indicates that something (such as a court or playing area) possesses a specific type of surface.
-
D.
servedOnCourt
Indicates that a person held an official judicial position on a particular court.
-
E.
positionInCourt
Indicates the specific role or standing an entity holds within a court setting or judicial proceeding.
- 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6121927e88190bdbfb05b37acaf3d |
completed | May 2, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 11:56 p.m.