Triple
T36999474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alþingi historical site |
E915311
|
entity |
| Predicate | foundedAsParliamentSiteIn |
P102418
|
FINISHED |
| Object | 930 |
—
|
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: 930 | Statement: [Alþingi historical site, foundedAsParliamentSiteIn, 930]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsParliamentSiteIn Context triple: [Alþingi historical site, foundedAsParliamentSiteIn, 930]
-
A.
usedAsSeatOfParliamentFrom
chosen
Indicates that a location functioned as the official meeting place of a parliament starting from a specified point in time.
-
B.
parliamentLocation
Indicates the place where a country's or region's parliament is situated or convenes.
-
C.
oneOfOldestParliamentsIn
Indicates that the subject is among the oldest parliaments located in the specified place or jurisdiction.
-
D.
establishedForParliament
Indicates that something (such as an institution, body, or arrangement) was created or set up specifically for the use, function, or purposes of a parliament.
-
E.
establishedAsModernParliament
Indicates that an institution or body was formally constituted or recognized as a modern parliamentary legislature.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff2fbae9b48190847eefa1c227d43e |
completed | May 9, 2026, 12:59 p.m. |
| PD | Predicate disambiguation | batch_69ff2f2218048190a32224a648182b5d |
completed | May 9, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:14 p.m.