Triple
T6221529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hibernia |
E139124
|
entity |
| Predicate | fieldNameOrigin |
P3325
|
FINISHED |
| Object | named after the Latin name for Ireland |
—
|
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: named after the Latin name for Ireland | Statement: [Hibernia, fieldNameOrigin, named after the Latin name for Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldNameOrigin Context triple: [Hibernia, fieldNameOrigin, named after the Latin name for Ireland]
-
A.
classOrigin
Indicates the original class or category from which an entity is derived, instantiated, or classified.
-
B.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
C.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
D.
physicalOrigin
Indicates that one entity is the place or source from which another entity physically originates or comes into existence.
-
E.
originallyBy
Indicates that one entity is the original creator, author, or source of 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062bcc2348190806ed8c98bdfbf3e |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.