Triple
T30463279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frashokereti |
E775067
|
entity |
| Predicate | worldStateAfterEvent |
P178649
|
FINISHED |
| Object | perfect |
—
|
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: perfect | Statement: [Frashokereti, worldStateAfterEvent, perfect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldStateAfterEvent Context triple: [Frashokereti, worldStateAfterEvent, perfect]
-
A.
capitalAfterEvent
Indicates that a location became the capital of a political or administrative entity as a result of, or following, a specific event.
-
B.
changesAfterEvents
chosen
Indicates that one entity undergoes a change as a consequence of, or following, the occurrence of specified events.
-
C.
hasWorldState
Indicates that an entity is associated with, or exists within, a particular overall configuration or condition of the world at a given time.
-
D.
maintainedAfterEvent
Indicates that a state, condition, or relationship continues to hold true after a specified event has occurred.
-
E.
legalStatusAfterEvent
Indicates the legal condition or classification an entity has as a result of a specified event or occurrence.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 29, 2026, 8:10 p.m.