Triple
T33477225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Morris Jr. |
E857357
|
entity |
| Predicate | fieldCorrespondentOn |
P156089
|
FINISHED |
| Object | Live PD |
—
|
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: Live PD | Statement: [Tom Morris Jr., fieldCorrespondentOn, Live PD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldCorrespondentOn Context triple: [Tom Morris Jr., fieldCorrespondentOn, Live PD]
-
A.
correspondentFor
chosen
Indicates that one entity serves as a correspondent or reporter on behalf of another entity, such as a media outlet, organization, or publication.
-
B.
fieldRepresents
Indicates that one field or attribute stands for, encodes, or symbolizes another concept, value, or entity.
-
C.
holderField
Indicates that a specified field or attribute belongs to, is maintained by, or is associated with a particular holder entity.
-
D.
fieldNamedFor
Indicates that a particular field (such as a sports field or open area) bears the name of a specified person, group, or entity in their honor.
-
E.
notableCorrespondent
Indicates that one entity is a significant or distinguished correspondent of another, typically through notable or historically important exchanges of communication.
- 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: May 1, 2026, 1:38 a.m.