Triple
T28279288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fishers, Indiana |
E713095
|
entity |
| Predicate | hasBusinessHub |
P9422
|
FINISHED |
| Object | Launch Fishers |
—
|
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: Launch Fishers | Statement: [Fishers, Indiana, hasBusinessHub, Launch Fishers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusinessHub Context triple: [Fishers, Indiana, hasBusinessHub, Launch Fishers]
-
A.
hasBusinessCenter
Indicates that an entity includes, contains, or is equipped with a business center facility.
-
B.
hasBusiness
Indicates that one entity owns, operates, or is formally associated with a business entity.
-
C.
isCommercialHubIn
chosen
Indicates that a place functions as a primary center of commercial or business activity within a specified larger area or region.
-
D.
hasBusinessNode
Indicates that an entity is associated with, linked to, or represented by a specific business-related node within a business structure or network.
-
E.
hasBusinessIn
Indicates that one entity conducts, operates, or maintains business activities within the jurisdiction, location, or domain of 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 11:21 p.m.