Triple
T30972557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohort |
E789136
|
entity |
| Predicate | takesSideIn |
P21606
|
FINISHED |
| Object | conflict between Lancelot and King Arthur |
—
|
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: conflict between Lancelot and King Arthur | Statement: [Bohort, takesSideIn, conflict between Lancelot and King Arthur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takesSideIn Context triple: [Bohort, takesSideIn, conflict between Lancelot and King Arthur]
-
A.
onSide
Indicates that one entity is positioned along or adjacent to the side of another entity.
-
B.
side
Indicates that one entity is located at, aligned with, or associated with the lateral part or edge of another entity.
-
C.
tookPositionOn
chosen
Indicates that an entity expressed or adopted a specific stance, opinion, or viewpoint regarding a particular issue, topic, or subject.
-
D.
targetSide
Indicates the specific side or aspect of a referenced target that is involved in or affected by the relationship or action.
-
E.
takenInBy
Indicates that one entity is absorbed, ingested, or otherwise brought inside and contained by another entity.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:55 p.m.