Triple
T472415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ithaca Commons |
E8586
|
entity |
| Predicate | typicalTenants |
P3277
|
FINISHED |
| Object | independent retailers |
—
|
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: independent retailers | Statement: [Ithaca Commons, typicalTenants, independent retailers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTenants Context triple: [Ithaca Commons, typicalTenants, independent retailers]
-
A.
anchorTenant
Indicates that an entity serves as a primary or major tenant whose presence helps attract other tenants or users to a shared space or platform.
-
B.
hasTenants
chosen
Indicates that an entity occupies or rents space from another entity as its tenant.
-
C.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eff24108819092fdb85019ec4089 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edecefb081908331ef8b9edf6636 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.