Triple
T33387139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falcarragh |
E854945
|
entity |
| Predicate | locatedInBarony |
P154320
|
FINISHED |
| Object | Kilmacrenan |
E1192188
|
NE 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: Kilmacrenan | Statement: [Falcarragh, locatedInBarony, Kilmacrenan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInBarony Context triple: [Falcarragh, locatedInBarony, Kilmacrenan]
-
A.
locatedInHistoricBarony
chosen
Indicates that one entity is situated within the geographical area of a historically recognized barony.
-
B.
hasBarony
Indicates that one entity possesses or is assigned authority over a barony associated with another entity.
-
C.
hasNotableBarony
Indicates that an entity possesses or is associated with a barony that is considered notable or significant in some context.
-
D.
companionBarony
Indicates a relationship where one barony is designated as an accompanying or associated barony to another, typically linked or paired in status or function.
-
E.
hasNumberOfCompanionBaronies
Indicates the specific count of companion baronies associated with a given entity.
- F. None of above.
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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a358148096c8190bdbd6dbd806a207c |
completed | June 19, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:35 a.m.