Triple
T21118275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cynewulfian canon |
E520354
|
entity |
| Predicate | hasDebatedAttribution |
P130986
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Cynewulfian canon, hasDebatedAttribution, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDebatedAttribution Context triple: [Cynewulfian canon, hasDebatedAttribution, true]
-
A.
hasDisputedAttribution
chosen
Indicates that the attribution of an entity (such as its creator, source, or origin) is contested or not universally agreed upon.
-
B.
hasSourceOfDebate
Indicates that something is the origin or cause of an ongoing disagreement, controversy, or dispute between parties.
-
C.
hasDebatedPerson
Indicates that one person has engaged in a debate or formal argumentative discussion with another person.
-
D.
hasDebatedStatus
Indicates that an entity has participated in or been assigned a particular status related to a debate or debating activity.
-
E.
hasDebatedMeaning
Indicates that the meaning or interpretation of something is contested, disputed, or subject to ongoing debate.
- 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e721078ac48190980441b6ada0e2b4 |
completed | April 21, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:55 p.m.