Triple
T37458152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morgl the Oracle |
E930849
|
entity |
| Predicate | controlSide |
P119113
|
FINISHED |
| Object | player hero |
—
|
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: player hero | Statement: [Morgl the Oracle, controlSide, player hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlSide Context triple: [Morgl the Oracle, controlSide, player hero]
-
A.
controlDirection
Indicates that one entity exerts influence or guidance over the orientation, course, or movement direction of another entity.
-
B.
controlledBySide2
chosen
Indicates that the object or resource is under the control, authority, or influence of the second party or side in a relationship or interaction.
-
C.
controlsSystem
Indicates that one entity has the authority or capability to direct, manage, or regulate the operation of a system.
-
D.
controlStand
Indicates that one entity manages, directs, or regulates the operation or behavior of another entity or system.
-
E.
controlMethods
Indicates the methods or techniques used by one entity to direct, regulate, or influence the behavior, operation, or state of 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff397e19a88190a945b826159f5290 |
completed | May 9, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69ff392400d0819088d30d08d4a774bd |
completed | May 9, 2026, 1:39 p.m. |
Created at: May 3, 2026, 4:17 p.m.