Triple
T34221690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glencree Valley |
E877937
|
entity |
| Predicate | hasNearbyHistoricalUse |
P51359
|
FINISHED |
| Object | military barracks at Glencree |
—
|
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: military barracks at Glencree | Statement: [Glencree Valley, hasNearbyHistoricalUse, military barracks at Glencree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHistoricalUse Context triple: [Glencree Valley, hasNearbyHistoricalUse, military barracks at Glencree]
-
A.
hasFormerUseNearby
chosen
Indicates that something in the vicinity previously had a particular use or function that is no longer current.
-
B.
hasHistoricalUsageIn
Indicates that something has been used or practiced within a particular historical period, context, or tradition.
-
C.
hasSharedHistoricalUse
Indicates that two or more entities have been used together or in a similar way within the same historical context or period.
-
D.
hasHistoricVicinity
Indicates that one entity is located near or within an area of historical significance associated with another entity.
-
E.
hasFormerUse
Indicates that something previously served a particular function or role that it no longer has.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffb5c373948190a6606e8caa87a384 |
completed | May 9, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ffb261da788190b41399df8ed895e8 |
completed | May 9, 2026, 10:17 p.m. |
Created at: May 1, 2026, 1:55 a.m.