Triple
T26826016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conchobar mac Nessa |
E675378
|
entity |
| Predicate | associatedWithCycle |
P43666
|
FINISHED |
| Object | Ulster Cycle |
—
|
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 Cycle | Statement: [Conchobar mac Nessa, associatedWithCycle, Ulster Cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCycle Context triple: [Conchobar mac Nessa, associatedWithCycle, Ulster Cycle]
-
A.
associatedKeyOfCycle
Indicates a relationship where a key is linked to or derived from a specific cycle within a process, structure, or system.
-
B.
includedInCycle
Indicates that an entity participates in and is part of a closed loop or recurring sequence within a system or structure.
-
C.
associatedWithAuthorCycle
Indicates a relationship where an entity is linked to a recurring or cyclical pattern involving an author, such as repeated collaborations, works, or roles over time.
-
D.
followedInCycleBy
Indicates that one entity directly succeeds another in a repeating or cyclical sequence.
-
E.
belongsToCycle
chosen
Indicates that an entity is part of, or contained within, a specific cycle or cyclic structure.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: April 27, 2026, 4:58 a.m.