Triple
T13256820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Yorker |
E315679
|
entity |
| Predicate | oftenIdentifiedBy |
P86837
|
FINISHED |
| Object | New York accent |
—
|
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: New York accent | Statement: [New Yorker, oftenIdentifiedBy, New York accent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenIdentifiedBy Context triple: [New Yorker, oftenIdentifiedBy, New York accent]
-
A.
alternativeIdentification
Indicates that one entity serves as an alternative identifier or reference for another entity.
-
B.
identifiedUsing
Indicates that one entity was recognized, distinguished, or determined by means of a specified method, tool, or identifier.
-
C.
commonlyIdentifiedWith
chosen
Indicates that two entities are widely regarded or treated as the same or equivalent, even if they are formally distinct.
-
D.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
E.
isTraditionallyIdentifiedAs
Indicates that one entity is customarily or historically recognized or labeled as being the same as, or corresponding to, another entity.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:24 p.m.