Triple
T37689539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aspelta |
E938465
|
entity |
| Predicate | movedCourtInfluence |
P122121
|
FINISHED |
| Object | towards southern regions of Kush |
—
|
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: towards southern regions of Kush | Statement: [Aspelta, movedCourtInfluence, towards southern regions of Kush]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movedCourtInfluence Context triple: [Aspelta, movedCourtInfluence, towards southern regions of Kush]
-
A.
movedCourtFrom
Indicates that an entity changed its legal venue or jurisdiction from one court to another.
-
B.
influencedRelocationOf
chosen
Indicates that one entity played a causal or motivating role in another entity’s decision or action to move from one location to another.
-
C.
movedOn
Indicates that an entity changed its position or location from one place to another at some point in time.
-
D.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
-
E.
influencesMovement
Indicates that one entity affects or alters the movement, motion, or trajectory 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.