Triple
T9625798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calymmian Period |
E232459
|
entity |
| Predicate | endAgeMa |
P89331
|
FINISHED |
| Object | 1400 |
—
|
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: 1400 | Statement: [Calymmian Period, endAgeMa, 1400]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endAgeMa Context triple: [Calymmian Period, endAgeMa, 1400]
-
A.
maximumAgeMa
Indicates that there is a specified maximum age limit applicable to an entity or relationship.
-
B.
startBoundaryAgeMa
Indicates the minimum age at which a male individual enters or becomes subject to a specified boundary, status, or condition.
-
C.
minimumAgeMa
Indicates that there is a specified minimum age requirement associated with an entity, below which the related action, status, or relationship is not permitted.
-
D.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
E.
approximateAgeMa
Indicates that one entity has an estimated or approximate age value relative to another reference (such as a person or event).
- F. None of above. chosen
Provenance (4 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9afb67c88190aa170716f0033752 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:10 p.m.