Triple
T33891410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matthew Malone |
E868776
|
entity |
| Predicate | centralEventsRevolveAround |
P181594
|
FINISHED |
| Object | Matthew Malone |
—
|
NE NERFINISHED |
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: Matthew Malone | Statement: [Matthew Malone, centralEventsRevolveAround, Matthew Malone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralEventsRevolveAround Context triple: [Matthew Malone, centralEventsRevolveAround, Matthew Malone]
-
A.
centralEventOfPiety
Indicates that an event serves as the primary or focal act of religious devotion or pious practice within a given context.
-
B.
storyEventsRevolveAround
chosen
Indicates that the central events or developments in a story primarily concern or are focused on a particular entity or subject.
-
C.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
D.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
E.
roundCoMainEvent
Indicates that an event serves as a co-main feature or secondary headline bout within a particular round of a larger event or competition.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 1, 2026, 1:48 a.m.