Triple
T592425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNESCO World Heritage tentative list |
E17304
|
entity |
| Predicate | isStepIn |
P9959
|
FINISHED |
| Object | World Heritage nomination process |
—
|
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: World Heritage nomination process | Statement: [UNESCO World Heritage tentative list, isStepIn, World Heritage nomination process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStepIn Context triple: [UNESCO World Heritage tentative list, isStepIn, World Heritage nomination process]
-
A.
hasStep
chosen
Indicates that one entity includes, is composed of, or is associated with a specific step or stage in a process involving another entity.
-
B.
isAt
Indicates that one entity is located at or present in the place or position of another entity.
-
C.
isOn
Indicates that one entity is physically positioned above and in contact with the top surface of another entity.
-
D.
isPositionOf
Indicates that one entity represents the spatial or organizational position or location of another entity.
-
E.
isInspected
Indicates that an entity is examined or checked by another entity to assess its condition, quality, or compliance.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bbcaf5c81908de4e27096d3da13 |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cd7d3c8190af008acf34a2293b |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.