Triple
T15679078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Occultation |
E377523
|
entity |
| Predicate | aimsAtOutcome |
P64674
|
FINISHED |
| Object | establishment of justice |
—
|
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: establishment of justice | Statement: [Occultation, aimsAtOutcome, establishment of justice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aimsAtOutcome Context triple: [Occultation, aimsAtOutcome, establishment of justice]
-
A.
aimOf
chosen
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
B.
outcomeFocus
Indicates that the primary emphasis or attention is placed on the results or consequences of an action or process.
-
C.
aimsToMeasure
Indicates that one entity is intended or designed to quantify, assess, or evaluate another entity or property.
-
D.
goalIn
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
-
E.
aimsToModel
Indicates that one entity is intended or designed to represent, simulate, or approximate the behavior, structure, or properties 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f2f1640819086efd5a73bb9734a |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.