Triple
T29190172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Jamillia |
E739968
|
entity |
| Predicate | positionEndContext |
P20778
|
FINISHED |
| Object | before the Clone Wars |
—
|
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: before the Clone Wars | Statement: [Queen Jamillia, positionEndContext, before the Clone Wars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionEndContext Context triple: [Queen Jamillia, positionEndContext, before the Clone Wars]
-
A.
positionStartContext
Indicates the contextual point or situation in which a position, role, or state first begins or is established.
-
B.
endOfPositionReason
Indicates the reason or cause for which a position, role, or employment relationship has come to an end.
-
C.
endOfRuleContext
Indicates that a particular parsing or evaluation rule has reached its terminating boundary within the current context.
-
D.
endOfTermContext
Indicates the situational or temporal context associated with the conclusion of a defined term, period, or contractual duration.
-
E.
notablePositionEnd
chosen
Indicates the point in time or event at which an entity’s notable position, role, or office comes to an end.
- 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: April 28, 2026, 12:01 p.m.