Triple
T37219567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lios na Scéithe |
E922837
|
entity |
| Predicate | hasHistoricalBarony |
P154320
|
FINISHED |
| Object | Magherastephana |
—
|
NE NERFINISHED |
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: Magherastephana | Statement: [Lios na Scéithe, hasHistoricalBarony, Magherastephana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalBarony Context triple: [Lios na Scéithe, hasHistoricalBarony, Magherastephana]
-
A.
historicBarony
Indicates that an entity has the status or role of a historic barony, i.e., it was once recognized as a baronial territorial or feudal jurisdiction.
-
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.
locatedInHistoricBarony
chosen
Indicates that one entity is situated within the geographical area of a historically recognized barony.
-
E.
isAmongOldestBaronies
Indicates that the barony is one of the earliest-established or longest-standing baronies within a given set or region.
- 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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: May 3, 2026, 4:15 p.m.