Triple
T15944117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO World Heritage documentation |
E386640
|
entity |
| Predicate | hasAccessFormat |
P6865
|
FINISHED |
| Object | online database |
—
|
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: online database | Statement: [UNESCO World Heritage documentation, hasAccessFormat, online database]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessFormat Context triple: [UNESCO World Heritage documentation, hasAccessFormat, online database]
-
A.
hasFileFormat
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
B.
hasAccessMode
chosen
Indicates the type or method of access that one entity is permitted to use with respect to another entity or resource.
-
C.
hasWorkingFormat
Indicates that one entity possesses or is associated with a functional or operational format of another entity.
-
D.
hasFormatCurrent
Indicates that an entity is available or expressed in the currently used or most up-to-date format.
-
E.
hasConfigurationFormat
Indicates that an entity uses or is associated with a specific configuration format for its settings or parameters.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.