Triple
T30926785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Branch |
E787878
|
entity |
| Predicate | locatedInLegendaryProvince |
P195238
|
FINISHED |
| Object | Ulster |
—
|
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: Ulster | Statement: [Red Branch, locatedInLegendaryProvince, Ulster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInLegendaryProvince Context triple: [Red Branch, locatedInLegendaryProvince, Ulster]
-
A.
legendaryHomeOf
Indicates that a place is traditionally or mythically regarded as the home or origin of a particular figure, group, or entity.
-
B.
locatedInProvinceHistorical
Indicates that an entity was situated within a specific province during a historical period or according to historical administrative boundaries.
-
C.
basedInLegend
chosen
Indicates that something is located, rooted, or primarily known within the context of a legend or mythic narrative.
-
D.
modernProvinceLocation
Indicates that a historical or former province is located within a specified modern administrative province or region.
-
E.
cultLocation
Indicates that a cult or religious group is based in, practices in, or is primarily associated with a particular location.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01302a80ec8190a27692f09ac38a80 |
completed | May 11, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_6a012fad62308190a53f8b4a071eb245 |
completed | May 11, 2026, 1:23 a.m. |
Created at: April 29, 2026, 8:51 p.m.