Triple
T14762418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Boca Raton, Florida |
E346899
|
entity |
| Predicate | bannedOutdoorBillboards |
P93006
|
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: [City of Boca Raton, Florida, bannedOutdoorBillboards, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bannedOutdoorBillboards Context triple: [City of Boca Raton, Florida, bannedOutdoorBillboards, true]
-
A.
hasSignageIn
Indicates that appropriate signs or signage for an entity are present or installed within a specified location or area.
-
B.
advertisingRestricted
chosen
Indicates that there are limitations or prohibitions on advertising activities associated with the related entities.
-
C.
bannedInContextOf
Indicates that something is prohibited or not allowed specifically within a particular situation, setting, or scope.
-
D.
hasSignage
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
-
E.
bannedInCountry
Indicates that something is officially prohibited or not allowed within the jurisdiction of a specified country.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7f207dc819088a53f717736a121 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.