Triple
T9337273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitzpatrick dynasty |
E224675
|
entity |
| Predicate | historicalLanguageSpoken |
P23402
|
FINISHED |
| Object | Early Modern Irish |
—
|
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: Early Modern Irish | Statement: [Fitzpatrick dynasty, historicalLanguageSpoken, Early Modern Irish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalLanguageSpoken Context triple: [Fitzpatrick dynasty, historicalLanguageSpoken, Early Modern Irish]
-
A.
historicallySpokenIn
Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
-
B.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
C.
languageOfHistoricalRecord
Indicates the language in which a given historical record is written or recorded.
-
D.
historicallySpoke
chosen
Indicates that an entity used a particular language as a spoken language during some period in the past.
-
E.
historicalLanguageRegion
Indicates that a language was historically spoken or used within a particular geographic region, regardless of its current status there.
- 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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd37f161e481908e23c1ec7e5fcf97 |
completed | April 1, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69cc7a66aef08190b8d668cff5b04f5f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:40 p.m.