Triple
T21591653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quintilis |
E532795
|
entity |
| Predicate | statusInModernUsage |
P144079
|
FINISHED |
| Object | historical name |
—
|
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: historical name | Statement: [Quintilis, statusInModernUsage, historical name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInModernUsage Context triple: [Quintilis, statusInModernUsage, historical name]
-
A.
contemporaryUse
Indicates that something is currently used or practiced in the present time or modern context.
-
B.
emergedInModernForm
Indicates that something developed into or appeared in its current recognizable form during the modern era.
-
C.
modernUse
Indicates how something is currently used or applied in modern times.
-
D.
modernUsageContext
Indicates the contemporary or current context in which something is used, applied, or functions.
-
E.
manyNowUsedAs
Indicates that numerous instances of an entity are currently being employed or serving in a particular role or function.
- 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_69e0c46251648190876f0427cf2d321b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eefaddc8508190950b31e2df865ad1 |
completed | April 27, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e63384a8fc819084c596bb53a3a1db |
completed | April 20, 2026, 2:09 p.m. |
Created at: April 16, 2026, 6:32 p.m.