Triple
T36237495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Reports |
E891413
|
entity |
| Predicate | reporterSeriesAbbreviation |
P114567
|
FINISHED |
| Object | N.Y. |
—
|
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: N.Y. | Statement: [New York Reports, reporterSeriesAbbreviation, N.Y.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reporterSeriesAbbreviation Context triple: [New York Reports, reporterSeriesAbbreviation, N.Y.]
-
A.
followsSeriesAbbreviation
Indicates that one entity is an abbreviation that comes after another entity in a series of abbreviations.
-
B.
reporterSeries
Indicates that a reporter is associated with, contributes to, or is part of a particular series of reports or stories.
-
C.
standardReporterAbbreviation
chosen
Indicates that one entity is the standardized abbreviated form of a reporter or reporting source name for another entity.
-
D.
reporterSeriesNumber
Indicates the numerical designation of a particular series within a set of reports or reporter publications.
-
E.
designationSeries
Indicates that one designation belongs to or is part of a broader series of related designations.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:09 p.m.