Triple
T23456443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caecilia |
E567933
|
entity |
| Predicate | nameOriginPeriod |
P34705
|
FINISHED |
| Object | classical antiquity |
—
|
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: classical antiquity | Statement: [Caecilia, nameOriginPeriod, classical antiquity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameOriginPeriod Context triple: [Caecilia, nameOriginPeriod, classical antiquity]
-
A.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
B.
formerNamePeriodStart
Indicates the date or time point when an entity began using a former name that is being recorded.
-
C.
etymologyPeriod
chosen
Indicates the historical time period during which a word’s form or meaning, as described by its etymology, was in use or originated.
-
D.
hasNameEtymologyIn
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
-
E.
nameEtymologyFor
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
- 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a6980d4481909fab47cb5bd28eab |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:53 p.m.