Triple
T35663910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pergamon and its Multi-Layered Cultural Landscape |
E1030512
|
entity |
| Predicate | whcCriteria |
P36515
|
FINISHED |
| Object | (iii) |
—
|
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: (iii) | Statement: [Pergamon and its Multi-Layered Cultural Landscape, whcCriteria, (iii)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: whcCriteria Context triple: [Pergamon and its Multi-Layered Cultural Landscape, whcCriteria, (iii)]
-
A.
selectionCriteria
Indicates the conditions or rules used to choose certain entities from a larger set.
-
B.
valueCriterion
Indicates that something is evaluated or selected based on a specified standard, rule, or measure of value.
-
C.
compositionCriterion
Indicates the rule or standard by which components are selected, combined, or arranged to form a whole.
-
D.
proposesCriterion
Indicates that one entity suggests or puts forward a specific criterion to be considered or used by another entity or within a given context.
-
E.
evaluationCriteriaInclude
chosen
Indicates that certain criteria are part of, or explicitly included in, the set of standards used to evaluate something.
- 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79faacec48190a5738e030b6f8808 |
completed | May 3, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.