Triple
T3697463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belle Glade culture |
E78492
|
entity |
| Predicate | hasTypeSite |
P44791
|
FINISHED |
| Object | Belle Glade site |
—
|
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: Belle Glade site | Statement: [Belle Glade culture, hasTypeSite, Belle Glade site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeSite Context triple: [Belle Glade culture, hasTypeSite, Belle Glade site]
-
A.
hasTypeSiteFor
chosen
Indicates that one entity serves as the specific site or location designated for a particular type or category of another entity.
-
B.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
-
D.
coversTypeOfSite
Indicates that one entity provides coverage or applies to a particular category or type of site.
-
E.
hasTypeSystem
Indicates that an entity employs, is governed by, or is associated with a particular type system (a defined set of rules for classifying and constraining types).
- 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_69ad85e3b1888190abc983e06968696d |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc5115ad8819085ffa938de3943f4 |
completed | March 8, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69adb84dc5808190850aa6975cb09e27 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:26 p.m.