Triple
T23586218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owen O’Malley |
E582350
|
entity |
| Predicate | supportingTo |
P1853
|
FINISHED |
| Object | Oscar Jaffee |
E626626
|
NE 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: Oscar Jaffee | Statement: [Owen O’Malley, supportingTo, Oscar Jaffee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportingTo Context triple: [Owen O’Malley, supportingTo, Oscar Jaffee]
-
A.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
B.
supportAgainst
Indicates providing help, resources, or advocacy to oppose or resist a particular target, threat, or adversary.
-
C.
support
chosen
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
-
D.
tendsToSupport
Indicates that one entity is generally inclined or likely to provide backing, assistance, or endorsement to another entity or its position.
-
E.
supportingWork
Indicates that one work provides assistance, reinforcement, or supplementary value to another work, helping to sustain or enhance it.
- F. None of above.
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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b03195748190b7e34f334902ac93 |
completed | April 29, 2026, 7:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0fe32ed3d08190a38a71c091e7a12a |
completed | May 22, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:41 p.m.