Triple
T10565491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tutuala |
E249338
|
entity |
| Predicate | hasCulturalHeritageNearby |
P48416
|
FINISHED |
| Object | rock art sites |
—
|
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: rock art sites | Statement: [Tutuala, hasCulturalHeritageNearby, rock art sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCulturalHeritageNearby Context triple: [Tutuala, hasCulturalHeritageNearby, rock art sites]
-
A.
hasNearbyCulturalDistrict
Indicates that an entity is located close to a designated cultural district or area with concentrated cultural activities.
-
B.
hasCulturalAttractions
chosen
Indicates that a place or entity possesses notable cultural points of interest, such as museums, theaters, historic sites, or artistic venues.
-
C.
nearbyWorldHeritageSite
Indicates that one entity is located close to, or in the immediate vicinity of, a designated World Heritage Site.
-
D.
nearbyArchaeologicalCulture
Indicates that one archaeological culture is geographically close to another archaeological culture.
-
E.
culturalHeritageOf
Indicates that something serves as the cultural heritage belonging to, originating from, or strongly associated with a particular entity or group.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5272c32c48190a92c1dacd4deb9fe |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:36 p.m.