Triple
T31183786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lydians |
E794979
|
entity |
| Predicate | treatyMediatedBy |
P65645
|
FINISHED |
| Object | Babylonians |
—
|
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: Babylonians | Statement: [Lydians, treatyMediatedBy, Babylonians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatyMediatedBy Context triple: [Lydians, treatyMediatedBy, Babylonians]
-
A.
treatyConcludedBy
Indicates that a treaty was formally agreed upon, finalized, or brought into effect by a specified party or parties.
-
B.
mediatorCountry
chosen
Indicates that a country acts as an intermediary or facilitator in resolving or managing a dispute, negotiation, or interaction between other parties.
-
C.
peaceTreatyWitnessedBy
Indicates that a peace treaty was formally observed or attested to by a specified witness or group of witnesses.
-
D.
treatyOf
Indicates a formal agreement or pact established between entities, typically states or organizations, defining their mutual obligations or terms.
-
E.
treatyConcluded
Indicates that a formal agreement or treaty has been officially finalized and brought into force between the involved parties.
- 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 9:08 p.m.