Triple
T3773500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inchcolm Abbey |
E83249
|
entity |
| Predicate | languageOfHistoricalUse |
P1434
|
FINISHED |
| Object | Latin |
—
|
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: Latin | Statement: [Inchcolm Abbey, languageOfHistoricalUse, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfHistoricalUse Context triple: [Inchcolm Abbey, languageOfHistoricalUse, Latin]
-
A.
languageOfHistoricalRecord
Indicates the language in which a given historical record is written or recorded.
-
B.
historicallySpokenIn
chosen
Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
-
C.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
D.
hasMajorityLanguageHistorically
Indicates that a particular language has historically been the predominant or majority language within a given entity or region.
-
E.
historicalLanguageGroup
Indicates that two or more entities belong to the same historically defined language group or family, based on shared linguistic ancestry or development.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc57c9e48190a0f254e47348bf32 |
completed | March 8, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69adc050cc5c81909d9855f866f3c26d |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:36 p.m.