Triple
T27341574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jud Wilson |
E684116
|
entity |
| Predicate | competitiveStyle |
P13362
|
FINISHED |
| Object | intense |
—
|
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: intense | Statement: [Jud Wilson, competitiveStyle, intense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitiveStyle Context triple: [Jud Wilson, competitiveStyle, intense]
-
A.
performanceStyle
chosen
Indicates the manner or style in which an action, work, or performance is carried out or presented.
-
B.
competitiveDiscipline
Indicates a relationship where an entity participates in or is associated with a structured, rule-based activity or field in which individuals or groups compete against each other.
-
C.
competitiveCategory
Indicates that two entities belong to the same market or activity segment in which they compete with one another.
-
D.
styleOfPlay
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
E.
competitiveEffect
Indicates that one entity’s actions or presence influence another entity’s ability to compete, typically by enhancing or diminishing its competitive position or performance.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 11:43 a.m.