Triple
T35045169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lukove beaches |
E1011175
|
entity |
| Predicate | hasSubFeature |
P25619
|
FINISHED |
| Object | Lukova Beach |
—
|
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: Lukova Beach | Statement: [Lukove beaches, hasSubFeature, Lukova Beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubFeature Context triple: [Lukove beaches, hasSubFeature, Lukova Beach]
-
A.
hasSubcomponent
chosen
Indicates that one entity is a constituent part or component of another, larger entity.
-
B.
hasIntermediateFeatures
Indicates that an entity possesses features or characteristics that are between two defined levels, states, or categories in a given context.
-
C.
hasSubproperty
Indicates that one property is a more specific version of another property, inheriting its meaning and constraints.
-
D.
hasSubService
Indicates that one service includes or is composed of another, more specific service as a subordinate or component part.
-
E.
hasSubordinateFunction
Indicates that one function operates under the authority, control, or scope of another function as its subordinate.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
Created at: May 3, 2026, 4:01 p.m.