Triple
T212485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WHS |
E4747
|
entity |
| Predicate | partOfTerminologySet |
P7659
|
FINISHED |
| Object | World Heritage terminology |
—
|
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 terminology | Statement: [WHS, partOfTerminologySet, World Heritage terminology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfTerminologySet Context triple: [WHS, partOfTerminologySet, World Heritage terminology]
-
A.
isPartOfStandard
chosen
Indicates that something belongs to, is included within, or conforms to a defined standard or standardized set.
-
B.
partlyDefinedBy
Indicates that one entity’s nature, role, or characteristics are only partially determined or specified by another entity.
-
C.
termType
Indicates the classification or category of a term within a system, specifying what kind of term it is (e.g., type, role, or function) in relation to others.
-
D.
terminologyNote
Indicates that there is an explanatory note or comment clarifying the use, meaning, or nuances of a specific term in the relationship.
-
E.
sets
Indicates that an entity places, positions, or puts another entity into a particular state, location, or configuration.
- 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c313d108190a65d3e939f961bef |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b509400819093a6c1a1bac861e3 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.