Triple
T32668379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MacAuliffe |
E835218
|
entity |
| Predicate | hasHistoricalLanguageForm |
P106922
|
FINISHED |
| Object | Mac Amhlaoibh |
—
|
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: Mac Amhlaoibh | Statement: [MacAuliffe, hasHistoricalLanguageForm, Mac Amhlaoibh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalLanguageForm Context triple: [MacAuliffe, hasHistoricalLanguageForm, Mac Amhlaoibh]
-
A.
hasLanguageFormOf
chosen
Indicates that one entity is a specific linguistic form, expression, or realization of the language used by another entity.
-
B.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
C.
historicalLanguageFeature
Indicates that a language possesses a feature, trait, or characteristic that existed or was relevant in a past historical period.
-
D.
hasMajorityLanguageHistorically
Indicates that a particular language has historically been the predominant or majority language within a given entity or region.
-
E.
historicalLanguageStatus
Indicates that a language had a particular official, social, or functional status during a past 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 1, 2026, 1:08 a.m.