Triple
T33713766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treriksröset |
E863814
|
entity |
| Predicate | earlierCairnBuilt |
P185345
|
FINISHED |
| Object | 1897 |
—
|
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: 1897 | Statement: [Treriksröset, earlierCairnBuilt, 1897]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierCairnBuilt Context triple: [Treriksröset, earlierCairnBuilt, 1897]
-
A.
earliestConstructionAttributedTo
Indicates that one entity is recognized as the earliest known construction project or built work attributed to another entity (such as a person, group, or organization).
-
B.
usesAncientStructure
Indicates that one entity makes use of, incorporates, or relies on an ancient structure in its function, design, or activity.
-
C.
earlierCultOnSite
Indicates that a religious cult or worship practice existed at a location prior to the one currently under consideration.
-
D.
earlierTomb
Indicates that one tomb chronologically predates another tomb.
-
E.
earlierFortificationCulture
Indicates that one culture’s fortification activity or tradition chronologically precedes that of another culture.
- F. None of above. chosen
Provenance (4 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be520f148190ba200bf3dbf40656 |
completed | May 3, 2026, 9:29 p.m. |
Created at: May 1, 2026, 1:44 a.m.