Triple
T33117184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayaz-Kala |
E847487
|
entity |
| Predicate | laterPhaseDate |
P201074
|
FINISHED |
| Object | 1st–2nd century CE |
—
|
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: 1st–2nd century CE | Statement: [Ayaz-Kala, laterPhaseDate, 1st–2nd century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPhaseDate Context triple: [Ayaz-Kala, laterPhaseDate, 1st–2nd century CE]
-
A.
mainPhaseDate
Indicates the date on which the primary or main phase of an event, process, or project occurs or is scheduled.
-
B.
secondPhaseStartDate
Indicates the date on which the second phase of a process, project, or activity begins.
-
C.
laterDuration
Indicates that one event or time interval occurs after another and lasts for a specified duration.
-
D.
firstPhaseEndDate
Indicates the date on which the first phase of a process, project, or activity is completed or scheduled to end.
-
E.
laterCreationDate
Indicates that one entity was created at a later date or time than the other entity.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
| PDg | Predicate description generation | batch_69ffc60504808190a89990b556b1d5ce |
completed | May 9, 2026, 11:40 p.m. |
Created at: May 1, 2026, 1:27 a.m.