Triple
T5986697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpringboardNYC |
E133243
|
entity |
| Predicate | basedInIndustryHub |
P51677
|
FINISHED |
| Object | New York City theater community |
—
|
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 City theater community | Statement: [SpringboardNYC, basedInIndustryHub, New York City theater community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedInIndustryHub Context triple: [SpringboardNYC, basedInIndustryHub, New York City theater community]
-
A.
isPartOfIndustry
Indicates that one entity belongs to, operates within, or is categorized under a particular industry sector.
-
B.
locatedInHubOf
chosen
Indicates that one entity is situated within the central hub or core area associated with another entity.
-
C.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
D.
hasNearbyIndustry
Indicates that an entity is located close to one or more industrial facilities or activities.
-
E.
isITHubOf
Indicates that an entity serves as a central location or primary center for IT-related activities, services, or operations for another entity or area.
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc38a308190a368c5c787a5fc64 |
completed | March 22, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c049de98648190962b14fd341c93da |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:04 p.m.