Triple
T27367849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James H. Bright |
E690220
|
entity |
| Predicate | notablePlaceDeveloped |
P63973
|
FINISHED |
| Object | Hialeah, Florida |
—
|
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: Hialeah, Florida | Statement: [James H. Bright, notablePlaceDeveloped, Hialeah, Florida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePlaceDeveloped Context triple: [James H. Bright, notablePlaceDeveloped, Hialeah, Florida]
-
A.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
B.
notableCityDeveloped
chosen
Indicates that a city was significantly developed, expanded, or shaped by the actions, planning, or investment of a particular agent or entity.
-
C.
notableCityOfDevelopment
Indicates that a particular city is especially significant or well-known as a primary place where something was developed or created.
-
D.
notablePlaceCreated
Indicates that an entity is the creator or originator of a particular notable place or location.
-
E.
developedAsTouristAttractionBy
Indicates that an entity was created, enhanced, or promoted as a tourist attraction by a specific agent or organization.
- 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69ffc3f0b19c8190b5a749bc3cad21dd |
completed | May 9, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69ffc1b882808190932b2d43ea5537c9 |
completed | May 9, 2026, 11:22 p.m. |
Created at: April 27, 2026, 12:17 p.m.