Triple
T27440102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rufus Buckley |
E690906
|
entity |
| Predicate | focusesOnHighProfileCase |
P31
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Rufus Buckley, focusesOnHighProfileCase, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnHighProfileCase Context triple: [Rufus Buckley, focusesOnHighProfileCase, true]
-
A.
handledHighProfileCase
Indicates that an entity has been responsible for managing or working on a case that is considered high-profile or widely notable.
-
B.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
C.
focusesOnCause
Indicates that an action, explanation, or analysis is directed toward identifying, examining, or emphasizing the underlying cause of something.
-
D.
specialFocus
Indicates that an entity receives particular attention, emphasis, or priority relative to others in a given context.
-
E.
hasHighProfileOwnership
Indicates that an entity is owned, controlled, or significantly invested in by a prominent or high-profile individual or organization.
- 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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 27, 2026, 12:44 p.m.