Triple
T30244505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spira |
E769018
|
entity |
| Predicate | appearsInImperialDocuments |
P150962
|
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, appearsInImperialDocuments, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInImperialDocuments Context triple: [Spira, appearsInImperialDocuments, true]
-
A.
attestedInWriting
Indicates that the relationship or fact is documented or confirmed in written form, such as in texts, records, or inscriptions.
-
B.
hasInscriptionFromReignOf
Indicates that an object bears an inscription created during the reign of a specified ruler or authority.
-
C.
attestedInInscriptions
Indicates that evidence for the entity is documented or recorded in one or more inscriptions.
-
D.
namedInHistoricalSources
chosen
Indicates that an entity is explicitly mentioned or identified in historical documents or records.
-
E.
hasImperialPeriod
Indicates that an entity is associated with, or belongs to, a specific imperial historical period.
- 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_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 29, 2026, 7:39 p.m.