Triple
T14528996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ó Flaithbheartaigh |
E340853
|
entity |
| Predicate | traditionalPrefix |
P7276
|
FINISHED |
| Object | Ó |
—
|
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: Ó | Statement: [Ó Flaithbheartaigh, traditionalPrefix, Ó]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalPrefix Context triple: [Ó Flaithbheartaigh, traditionalPrefix, Ó]
-
A.
standardPrefix
chosen
Indicates that one entity serves as the conventional or officially recognized prefix used before another entity.
-
B.
traditionalPrecedence
Indicates that one entity is accorded higher status, priority, or rank over another according to established tradition or customary order.
-
C.
traditionalBase
Indicates that one entity serves as the customary or historically established foundation or basis for another.
-
D.
traditionalStyle
Indicates that something follows or embodies a conventional, long-established way of doing, making, or presenting it, in contrast to modern or innovative styles.
-
E.
namespacePrefix
Indicates the abbreviated prefix string associated with a particular namespace URI in a naming or identifier system.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea051bc608190ad4d516c5e7bca43 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.