Triple
T13177632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boyne Valley |
E313141
|
entity |
| Predicate | periodOfMajorMonumentConstruction |
P22153
|
FINISHED |
| Object | Neolithic |
—
|
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: Neolithic | Statement: [Boyne Valley, periodOfMajorMonumentConstruction, Neolithic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodOfMajorMonumentConstruction Context triple: [Boyne Valley, periodOfMajorMonumentConstruction, Neolithic]
-
A.
eraOfMajorConstruction
chosen
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
B.
monumentConstructionStart
Indicates the date or time when the construction of a monument was begun.
-
C.
royalPalaceConstructionPeriod
Indicates the time span during which a royal palace was built or under construction.
-
D.
eraOfOriginalMonuments
Indicates the historical time period during which the original monuments were created or first established.
-
E.
timePeriodOfArchitecture
Indicates the historical time period or era during which a particular architectural work, style, or feature was created or predominantly used.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.