Triple
T23626458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Drama Critics Circle |
E583478
|
entity |
| Predicate | hasMemberLocation |
P105146
|
FINISHED |
| Object | New York-based |
—
|
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-based | Statement: [New York Drama Critics Circle, hasMemberLocation, New York-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberLocation Context triple: [New York Drama Critics Circle, hasMemberLocation, New York-based]
-
A.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
B.
membershipLocation
chosen
Indicates that an entity’s membership or affiliation is associated with, based in, or held at a particular location.
-
C.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
D.
hasMemberMunicipality
Indicates that an administrative region or governing body includes a specific municipality as one of its constituent members.
-
E.
hasActLocation
Indicates that an action or event occurs at, or is associated with, a specific location.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b17d4f508190abbb508746bfebb9 |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.