Triple
T31857924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gortyna |
E813245
|
entity |
| Predicate | legalTextDate |
P134468
|
FINISHED |
| Object | 5th century BCE (approximate) |
—
|
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: 5th century BCE (approximate) | Statement: [Gortyna, legalTextDate, 5th century BCE (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalTextDate Context triple: [Gortyna, legalTextDate, 5th century BCE (approximate)]
-
A.
dateOfTextualForm
chosen
Indicates the date associated with the creation, writing, or specific textual version of a work or document.
-
B.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
C.
legalTermStart
Indicates that a specified legal term, period, or contractual timeframe begins at a particular point in time.
-
D.
date
Indicates that two entities are engaged in or participate in a romantic or social outing or relationship with each other.
-
E.
issuedDocumentDate
Indicates the date on which a document was formally created, released, or made officially valid by the issuing party.
- 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
Created at: April 30, 2026, 11:52 p.m.