Triple
T30244507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spira |
E769018
|
entity |
| Predicate | usedInLatinHistoriography |
P97178
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Spira, usedInLatinHistoriography, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInLatinHistoriography Context triple: [Spira, usedInLatinHistoriography, true]
-
A.
usedInLateAntiquity
Indicates that something was in use or actively employed during the historical period of Late Antiquity.
-
B.
eraNameUsedInHistoriography
Indicates that a particular historical era name is used within historiographical writing or scholarship to refer to a period or context.
-
C.
historicalNameInLatin
chosen
Indicates that an entity has a historically used name expressed in Latin.
-
D.
hasHistoriographicalUse
Indicates that something is used or cited within historical writing or analysis as part of constructing, interpreting, or debating historical narratives.
-
E.
usedInHistoricalPolity
Indicates that something (such as a name, title, or term) was employed or attested within the context of a specific historical polity or political 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: April 29, 2026, 7:39 p.m.