Triple
T32991532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lehigh Acres |
E844099
|
entity |
| Predicate | developmentCompany |
P4120
|
FINISHED |
| Object | Lehigh Acres Development Corporation |
—
|
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: Lehigh Acres Development Corporation | Statement: [Lehigh Acres, developmentCompany, Lehigh Acres Development Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentCompany Context triple: [Lehigh Acres, developmentCompany, Lehigh Acres Development Corporation]
-
A.
companyTypeOfDeveloper
Indicates that a given company is the type or category of organization that a particular developer belongs to or works for.
-
B.
majorDeveloper
Indicates that an entity is a primary or leading developer responsible for creating or significantly contributing to another entity.
-
C.
hasDevelopmentStudioIn
Indicates that an entity has a development studio located in a specified place.
-
D.
developerSubsidiaryOf
Indicates that a developer entity operates as a subsidiary under the ownership or control of another (parent) entity.
-
E.
company
chosen
Indicates that an entity is a business organization engaged in commercial, industrial, or professional activities.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 1, 2026, 1:22 a.m.