Triple
T26802122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old North |
E671128
|
entity |
| Predicate | hasNotableTextualSource |
P142947
|
FINISHED |
| Object | Y Gododdin |
—
|
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: Y Gododdin | Statement: [Old North, hasNotableTextualSource, Y Gododdin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableTextualSource Context triple: [Old North, hasNotableTextualSource, Y Gododdin]
-
A.
hasNotabilitySource
Indicates that there exists an external, recognized source that attests to or supports the notability or significance of the subject entity.
-
B.
hasNotableCorpus
Indicates that an entity possesses a significant, well-recognized body of work, texts, or collected materials associated with it.
-
C.
notableManuscriptSource
chosen
Indicates that one entity serves as a significant or historically important manuscript source for another entity.
-
D.
hasNotableReference
Indicates that one entity makes a significant or noteworthy mention of, or allusion to, another entity.
-
E.
hasTextualTransmission
Indicates that a work, idea, or content has been passed down, preserved, or conveyed through written or textual forms over time.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: April 27, 2026, 4:23 a.m.