Triple
T22623208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northeast Opelika Industrial Park |
E558340
|
entity |
| Predicate | intendedTenants |
P96896
|
FINISHED |
| Object | industrial companies |
—
|
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: industrial companies | Statement: [Northeast Opelika Industrial Park, intendedTenants, industrial companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedTenants Context triple: [Northeast Opelika Industrial Park, intendedTenants, industrial companies]
-
A.
intendedTenant
chosen
Indicates that one entity is designated or expected to occupy or lease another entity (such as a property) as a tenant.
-
B.
intendedResidents
Indicates the people or entities for whom a place, dwelling, or facility is designed or meant to be occupied by.
-
C.
tenantsEndUse
Indicates that the specified end use or consumption activity is carried out by tenants rather than by the property owner or other parties.
-
D.
tenantsSupport
Indicates that one or more tenants provide backing, endorsement, or assistance to another entity or cause.
-
E.
tenantsStart
Indicates that a tenancy relationship begins or is initiated at a specific time or event.
- 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_69e24545a8e08190bfa7482a2c725ff1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e3b97f8819082ea2b23ff4b2173 |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3:01 p.m.