Triple
T31142625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ossory |
E793829
|
entity |
| Predicate | anglicisedFrom |
P139362
|
FINISHED |
| Object | Osraige |
—
|
NE NERFINISHED |
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: Osraige | Statement: [Ossory, anglicisedFrom, Osraige]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: anglicisedFrom Context triple: [Ossory, anglicisedFrom, Osraige]
-
A.
historicallyAnglicisedDuring
Indicates that an entity’s name or form was historically rendered into an Anglicised version during a specified time period.
-
B.
dynasticSurnameAnglicisedAs
Indicates that a dynastic surname has an established or commonly used anglicized form derived from its original language.
-
C.
historicalNameInEnglish
chosen
Indicates that an entity is associated with a historical English-language name by which it was known in the past.
-
D.
hasLaterNameInEnglish
Indicates that an entity is known by a different English name at a later time or in a subsequent context.
-
E.
derivedFromEarlierEnglishName
Indicates that one name originates from or is historically developed out of an earlier English name.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:06 p.m.