Triple
T3642193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agesilaus |
E77213
|
entity |
| Predicate | evaluativeStance |
P3406
|
FINISHED |
| Object | highly favorable toward Agesilaus II |
—
|
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: highly favorable toward Agesilaus II | Statement: [Agesilaus, evaluativeStance, highly favorable toward Agesilaus II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaluativeStance Context triple: [Agesilaus, evaluativeStance, highly favorable toward Agesilaus II]
-
A.
editorialStance
Indicates the position, viewpoint, or bias an editor or publication adopts toward a subject, issue, or entity.
-
B.
hasAuthorialStance
Indicates that an entity expresses, embodies, or is associated with a particular author’s viewpoint, attitude, or perspective toward its subject matter.
-
C.
evaluationBasis
Indicates the criteria, standards, or reference framework used to judge, assess, or measure something in an evaluation process.
-
D.
ratingContext
Indicates the situational or contextual factors under which a rating is given or applies.
-
E.
stance
chosen
Indicates the position, attitude, or viewpoint one entity holds toward another entity, issue, or proposition.
- 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc359a91481908aef1c022f45e55c |
completed | March 8, 2026, 6:43 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.