Triple
T23583967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inventory of Swiss Heritage Sites |
E582283
|
entity |
| Predicate | levelOfSignificance |
P15465
|
FINISHED |
| Object | national |
—
|
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: national | Statement: [Inventory of Swiss Heritage Sites, levelOfSignificance, national]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelOfSignificance Context triple: [Inventory of Swiss Heritage Sites, levelOfSignificance, national]
-
A.
typeOfSignificance
chosen
Indicates that one entity specifies the nature or category of importance, relevance, or significance that another entity possesses.
-
B.
statisticalLevel
Indicates the degree or tier of statistical detail, aggregation, or granularity at which data or analysis is defined or reported.
-
C.
rankSignificance
Indicates how important or influential one entity is relative to others within a specified context or ordering.
-
D.
significance
Indicates that one entity holds particular importance, influence, or meaningful impact in relation to another entity or context.
-
E.
confidenceLevel
Indicates the degree of certainty or assurance associated with a particular claim, decision, or outcome.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b02f68288190b348c7558a6a24e1 |
completed | April 29, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:40 p.m.