Triple
T16600667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin League |
E403320
|
entity |
| Predicate | treatyDateApproximate |
P23330
|
FINISHED |
| Object | 493 BC |
—
|
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: 493 BC | Statement: [Latin League, treatyDateApproximate, 493 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatyDateApproximate Context triple: [Latin League, treatyDateApproximate, 493 BC]
-
A.
treatyDate
Indicates the calendar date on which a treaty is formally agreed upon, signed, or comes into effect between parties.
-
B.
treatyConcludedAfter
Indicates that one treaty was formally concluded at a later time than another specified treaty.
-
C.
treatySignedYear
chosen
Indicates the calendar year in which a specific treaty was formally signed.
-
D.
treatySettlementYear
Indicates the year in which a treaty was formally settled or concluded.
-
E.
treatyEnteredIntoForce
Indicates that a treaty has become legally binding and operative for the parties involved after meeting its specified conditions for entry into force.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d75772c8190b02aef02ea6788e1 |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.