Triple
T33624148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raetic alphabet |
E861351
|
entity |
| Predicate | timeOfDisuse |
P61343
|
FINISHED |
| Object | around 1st century BCE |
—
|
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: around 1st century BCE | Statement: [Raetic alphabet, timeOfDisuse, around 1st century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfDisuse Context triple: [Raetic alphabet, timeOfDisuse, around 1st century BCE]
-
A.
periodOfAbandonment
chosen
Indicates a time span during which something is left unused, unattended, or not maintained.
-
B.
timeBetweenCensusAndUse
Indicates the length of time that passes between when a census is conducted and when its data is used for a particular purpose.
-
C.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
D.
lastUsedFor
Indicates that one entity was the most recent purpose, function, or application for which another entity was used.
-
E.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
- 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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 1, 2026, 1:41 a.m.