Triple
T24958997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbey of San Fruttuoso |
E624550
|
entity |
| Predicate | seclusion |
P34695
|
FINISHED |
| Object | secluded coastal bay |
—
|
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: secluded coastal bay | Statement: [Abbey of San Fruttuoso, seclusion, secluded coastal bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seclusion Context triple: [Abbey of San Fruttuoso, seclusion, secluded coastal bay]
-
A.
hasSeclusion
chosen
Indicates that one entity provides, involves, or is characterized by a state or condition of privacy, isolation, or separation from others for another entity.
-
B.
seclusionRanking
Indicates the relative degree to which something is isolated or set apart from others compared to similar things.
-
C.
solitary
Indicates that an entity exists, acts, or is characterized in isolation, without the presence or involvement of others.
-
D.
isolatedBy
Indicates that one entity has been separated or kept apart from another entity or set of entities, preventing interaction or influence between them.
-
E.
containment
Indicates that one entity is spatially or conceptually enclosed within the boundaries or scope of another entity.
- 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_69e2ff23a3a88190b1b9743fe5e15f94 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4242b03a081909c676b1884191f17 |
completed | May 1, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:58 a.m.