Triple
T18804070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eschborn |
E459827
|
entity |
| Predicate | isBusinessCenter |
P133075
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Eschborn, isBusinessCenter, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBusinessCenter Context triple: [Eschborn, isBusinessCenter, true]
-
A.
hasBusinessCenter
Indicates that an entity includes, contains, or is equipped with a business center facility.
-
B.
isInBusinessDistrict
Indicates that an entity is located within a designated business or commercial district area.
-
C.
isCommercialFacility
Indicates that a facility is used primarily for commercial or business-related activities or services.
-
D.
isBusinessRoute
Indicates that a route functions primarily for business-related travel or commercial purposes between locations.
-
E.
centralBusiness
Indicates that an entity functions as the primary commercial or economic hub (central business area or role) in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a025faf48190be07086071df5b34 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:53 a.m.