Triple
T35100176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persica |
E1012987
|
entity |
| Predicate | authorServedAtCourtOf |
P195912
|
FINISHED |
| Object | Artaxerxes II of Persia |
—
|
NE NERFINISHED |
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: Artaxerxes II of Persia | Statement: [Persica, authorServedAtCourtOf, Artaxerxes II of Persia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorServedAtCourtOf Context triple: [Persica, authorServedAtCourtOf, Artaxerxes II of Persia]
-
A.
authorOfWorkAppearingIn
Indicates that one entity is the creator or writer of a work that appears within another work or publication.
-
B.
authorPublished
Indicates that an author has published a particular work (such as a book, article, or paper).
-
C.
authorPositionAtTimeOfPublication
Indicates the specific role or position an author held at the time a work was published.
-
D.
authoredWith
Indicates that two or more entities jointly created or wrote a work together.
-
E.
authorOfLegalOpinion
Indicates that a person is the writer or creator of a specific legal opinion document.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69fdee75d1408190bba58a9cef200a54 |
completed | May 8, 2026, 2:08 p.m. |
Created at: May 3, 2026, 4:01 p.m.