Triple
T15181933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian satraps |
E362766
|
entity |
| Predicate | wereSometimes |
P26764
|
FINISHED |
| Object | local dynasts |
—
|
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: local dynasts | Statement: [Persian satraps, wereSometimes, local dynasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wereSometimes Context triple: [Persian satraps, wereSometimes, local dynasts]
-
A.
wasA
Indicates that an entity previously had a certain role, type, or classification in the past.
-
B.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
C.
wereInternedBy
Indicates that an entity was forcibly confined, detained, or held in an internment facility by another entity (typically an authority or government).
-
D.
wasPowerfulIn
Indicates that an entity possessed significant power, influence, or effectiveness within a specified domain, context, or time period.
-
E.
wasAmong
chosen
Indicates that an entity belonged to, was included in, or was part of a particular group, set, or collection.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006663ad48190986b680001be0e9b |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.