Triple
T33774204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridge of the Ford |
E865466
|
entity |
| Predicate | glosses |
P97872
|
FINISHED |
| Object | meaning of the Irish name for Drogheda |
—
|
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: meaning of the Irish name for Drogheda | Statement: [Bridge of the Ford, glosses, meaning of the Irish name for Drogheda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: glosses Context triple: [Bridge of the Ford, glosses, meaning of the Irish name for Drogheda]
-
A.
meaningGloss
Indicates that the predicate provides a brief explanatory phrase or paraphrase capturing the meaning or sense of another expression or item.
-
B.
hasGlossonym
Indicates a relationship where an entity is associated with the specific name or term used to refer to a language (its glossonym).
-
C.
hasMultilingualGlosses
Indicates that an entity is associated with glosses or explanatory labels available in multiple languages.
-
D.
hasGloss
Indicates that one entity provides a textual definition or explanatory gloss for another entity.
-
E.
hasEnglishGloss
chosen
Indicates that one entity serves as the English-language gloss or explanatory translation for the other entity.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.