Triple
T33563149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camus |
E859680
|
entity |
| Predicate | hasIrish-speakingCommunity |
P5562
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Camus, hasIrish-speakingCommunity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIrish-speakingCommunity Context triple: [Camus, hasIrish-speakingCommunity, yes]
-
A.
hasSignificantIrishCommunity
Indicates that a place or region contains a notably large or influential population of people of Irish origin or heritage.
-
B.
hasLanguageCommunity
chosen
Indicates that an entity is associated with or serves a particular language community.
-
C.
isGaeltacht
Indicates that a place or region is officially recognized as part of the Irish-speaking Gaeltacht area.
-
D.
containsGaeltachtArea
Indicates that a region or administrative area includes within its boundaries a Gaeltacht area where Irish is traditionally spoken.
-
E.
hasNeighboringLanguageCommunity
Indicates that one language community is geographically or socially adjacent to another, allowing for direct contact or interaction between them.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f714fe7c819095c70dcf4164ed24 |
completed | May 3, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.