Triple
T13220484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antalcidas Peace |
E314738
|
entity |
| Predicate | imposedTerms |
P7925
|
FINISHED |
| Object | Persian-dictated terms |
—
|
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: Persian-dictated terms | Statement: [Antalcidas Peace, imposedTerms, Persian-dictated terms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imposedTerms Context triple: [Antalcidas Peace, imposedTerms, Persian-dictated terms]
-
A.
imposes
chosen
Indicates that one entity enforces, applies, or places a rule, condition, burden, or obligation upon another entity.
-
B.
imposedOn
Indicates that one party enforces, applies, or places a requirement, burden, or constraint onto another party or entity.
-
C.
surrenderTerms
Indicates the conditions or stipulations under which one party formally yields or capitulates to another.
-
D.
restrictionOfPact
Indicates a relationship where one pact imposes limitations, conditions, or constraints on another pact or agreement.
-
E.
legalTermIn
Indicates that a particular legal term or concept is used, defined, or applicable within a specified legal document, jurisdiction, or context.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf581508190883033f0c961736a |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:18 p.m.