Triple
T7528319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europeans |
E177952
|
entity |
| Predicate | hasHistoricalHeritage |
P10915
|
FINISHED |
| Object | European history |
—
|
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: European history | Statement: [Europeans, hasHistoricalHeritage, European history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalHeritage Context triple: [Europeans, hasHistoricalHeritage, European history]
-
A.
hasHeritageValueFor
Indicates that something possesses cultural, historical, or heritage significance for a particular entity or community.
-
B.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
C.
heritageValue
chosen
Indicates that something possesses cultural, historical, or traditional significance that is valued and preserved as heritage.
-
D.
isPartOfHeritage
Indicates that something belongs to, contributes to, or is recognized as a component of a broader cultural, historical, or natural heritage.
-
E.
hasHeritageFeature
Indicates that an entity possesses or includes a feature recognized as part of cultural, historical, or natural heritage.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f81e19208190965f211d057f7fdf |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.