Triple
T2128055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perico |
E46469
|
entity |
| Predicate | settingOfAppearance |
P1957
|
FINISHED |
| Object | Cuban fishing village |
—
|
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: Cuban fishing village | Statement: [Perico, settingOfAppearance, Cuban fishing village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfAppearance Context triple: [Perico, settingOfAppearance, Cuban fishing village]
-
A.
adaptationAppearance
Indicates that one entity appears or is depicted in an adaptation of another entity (such as a work being represented in a derived or reinterpreted version).
-
B.
appearance
Indicates how something looks or seems to an observer, including its visible form, condition, or outward impression.
-
C.
featuresSetting
Indicates that something includes, presents, or highlights a particular setting as a notable or primary aspect.
-
D.
userInterfaceStyle
Indicates the visual presentation mode or theme (such as light or dark) that the user interface is currently using or configured to use.
-
E.
setting
chosen
Indicates the place, time, or context in which an event, action, or interaction occurs.
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb75033881909b16659fc73945ef |
completed | March 7, 2026, 5:45 a.m. |
| PD | Predicate disambiguation | batch_69abb7bd86cc8190938ef06c1ed6d969 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.