Triple
T27064145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 31 of the Constitution of Ireland |
E685126
|
entity |
| Predicate | hasEqualAuthenticTextIn |
P155511
|
FINISHED |
| Object | English language |
—
|
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: English language | Statement: [Article 31 of the Constitution of Ireland, hasEqualAuthenticTextIn, English language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEqualAuthenticTextIn Context triple: [Article 31 of the Constitution of Ireland, hasEqualAuthenticTextIn, English language]
-
A.
authenticTextIn
chosen
Indicates that a given text is the authoritative or original version of a work within a specified context, source, or collection.
-
B.
isAuthentic
Indicates that something is genuine, real, or true to its claimed origin, nature, or standard.
-
C.
hasTextBy
Indicates that one entity (such as a document, work, or record) contains or is associated with text authored or written by another entity.
-
D.
hasText
Indicates that an entity is associated with or contains a specific piece of textual content.
-
E.
containsTextsFor
Indicates that one entity holds or includes text content intended for use by another 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 8:23 a.m.