Triple
T14231471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongol–Java conflict (1293) |
E352760
|
entity |
| Predicate | outcomeForJava |
P59870
|
FINISHED |
| Object | consolidation of power under Raden Wijaya |
—
|
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: consolidation of power under Raden Wijaya | Statement: [Mongol–Java conflict (1293), outcomeForJava, consolidation of power under Raden Wijaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForJava Context triple: [Mongol–Java conflict (1293), outcomeForJava, consolidation of power under Raden Wijaya]
-
A.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
B.
outcomeType
Indicates the specific category or nature of the result produced by an event, process, or action.
-
C.
outcomeOfTrial
Indicates that a particular result or verdict is produced as the consequence of a specific trial or legal proceeding.
-
D.
resultDetermination
Indicates the process or criteria by which an outcome, decision, or result is established or concluded from given inputs or conditions.
-
E.
outcomeOffice
Indicates that an outcome or result is associated with, produced by, or realized within a particular office or administrative unit.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de622b89fc8190af08dab9e1976759 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.