Triple
T9622965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mauretania Tingitana |
E232389
|
entity |
| Predicate | startTimeDetail |
P89312
|
FINISHED |
| Object | after 40 AD |
—
|
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: after 40 AD | Statement: [Mauretania Tingitana, startTimeDetail, after 40 AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeDetail Context triple: [Mauretania Tingitana, startTimeDetail, after 40 AD]
-
A.
startTimeNote
Indicates the specific time-related note or annotation associated with when an event or action begins.
-
B.
timeStatus
Indicates the temporal state or condition of an event or entity relative to a reference time (e.g., past, present, future, ongoing, or scheduled).
-
C.
spentTimeIn
Indicates that an entity has spent a certain amount or period of time in a particular place or context.
-
D.
positionStartTime
Indicates the time at which a position, role, or placement begins.
-
E.
startTimeAsCardinal
Indicates the specific clock time at which an event or action begins, expressed as a cardinal (numeric) value rather than a textual or formatted time.
- 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_69cd9ad650a4819096258665bc3f410b |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
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.