Triple
T27357854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ætheling |
E685734
|
entity |
| Predicate | usedInSourceLanguageScript |
P180010
|
FINISHED |
| Object | Latinized medieval charters |
—
|
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: Latinized medieval charters | Statement: [Ætheling, usedInSourceLanguageScript, Latinized medieval charters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInSourceLanguageScript Context triple: [Ætheling, usedInSourceLanguageScript, Latinized medieval charters]
-
A.
usedInLanguage
Indicates that something (such as a word, expression, or symbol) is employed or occurs within a particular language.
-
B.
usedInScripts
Indicates that something (such as a tool, method, or resource) is employed or referenced within one or more scripts.
-
C.
scriptUsedForLanguage
Indicates that a particular writing script is employed to write or represent a given language.
-
D.
usesScriptFor
Indicates that one entity employs or relies on a particular script or writing system for its representation, communication, or operation.
-
E.
usedAsSourceIn
Indicates that something serves as the origin, basis, or input from which another thing is derived, produced, or obtained.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 27, 2026, 11:52 a.m.