Triple
T37932469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Audley |
E946253
|
entity |
| Predicate | historicalSpellingStatus |
P203693
|
FINISHED |
| Object | archaic form of Audley |
—
|
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: archaic form of Audley | Statement: [de Audley, historicalSpellingStatus, archaic form of Audley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalSpellingStatus Context triple: [de Audley, historicalSpellingStatus, archaic form of Audley]
-
A.
spellingStyle
Indicates the particular orthographic convention or system of spelling that is used or preferred in a given context.
-
B.
scripturalSpelling
Indicates that one form of a word or name is the spelling used in a particular scriptural or sacred text.
-
C.
hasStandardOrthographySince
Indicates that a language or writing system has used a particular standardized orthography starting from a specified point in time.
-
D.
colonialEraSpellingOf
Indicates that one term is the spelling of another term as it was used during the colonial era.
-
E.
currentOfficialSpelling
Indicates the officially recognized and currently valid spelling form of a given name or term.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a01c74a72fc819084826c6c292af03a |
completed | May 11, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_6a01c624103c819087cb35a71c5868b6 |
completed | May 11, 2026, 12:05 p.m. |
| PDg | Predicate description generation | batch_6a01c749c7148190ad49ede859c60b75 |
completed | May 11, 2026, 12:10 p.m. |
Created at: May 3, 2026, 4:20 p.m.