Triple
T3203016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Knight |
E67094
|
entity |
| Predicate | challengesWith |
P41797
|
FINISHED |
| Object | beheading game |
—
|
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: beheading game | Statement: [Green Knight, challengesWith, beheading game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: challengesWith Context triple: [Green Knight, challengesWith, beheading game]
-
A.
challengedPractice
Indicates that one entity has questioned, disputed, or formally opposed the validity, appropriateness, or continuation of another entity’s practice or procedure.
-
B.
hasChallenge
Indicates that an entity faces, experiences, or is confronted with a particular difficulty, obstacle, or problem.
-
C.
challengeUndertaken
chosen
Indicates that an entity has accepted and is actively engaging in a specific challenge or demanding task.
-
D.
challengeType
Indicates the specific category or kind of challenge associated with an action or relationship between entities.
-
E.
constructionChallenges
Indicates difficulties, obstacles, or complications encountered during the process of constructing or building something.
- 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada9b188a88190b7b5e9b3be9410db |
completed | March 8, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.