Triple
T15181932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian satraps |
E362766
|
entity |
| Predicate | wereOften |
P117030
|
FINISHED |
| Object | members of Persian nobility |
—
|
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: members of Persian nobility | Statement: [Persian satraps, wereOften, members of Persian nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wereOften Context triple: [Persian satraps, wereOften, members of Persian nobility]
-
A.
oftenSays
Indicates that one entity frequently makes a particular statement or remark, or regularly expresses a certain idea or phrase.
-
B.
oftenSucceeded
Indicates that one entity frequently or repeatedly follows another in a sequence of successes or outcomes.
-
C.
oftenPrecededBy
Indicates that one event, state, or item commonly occurs or appears before another in time or sequence.
-
D.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
-
E.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:09 a.m.