Triple
T16600673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latin League |
E403320
|
entity |
| Predicate | dissolutionDateApproximate |
P102082
|
FINISHED |
| Object | 338 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: 338 BC | Statement: [Latin League, dissolutionDateApproximate, 338 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissolutionDateApproximate Context triple: [Latin League, dissolutionDateApproximate, 338 BC]
-
A.
hasDissolutionDate
Indicates the date on which an entity, such as an organization or legal arrangement, formally ceases to exist or is officially dissolved.
-
B.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
-
C.
dissolutionTime
Indicates the point in time at which a relationship, structure, or entity ceases to exist or is formally terminated.
-
D.
disbandedAt
Indicates the time or date at which an organized group, body, or entity formally ceased to exist or operate.
-
E.
dissolvedOnOrAround
chosen
Indicates that an entity ceased to exist, function, or remain in force on or approximately around a specified date.
- 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_69e35d764574819081366374ca0c9bea |
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.