Triple
T34463773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tower of Light |
E884713
|
entity |
| Predicate | hasLanguageOfNameOrigin |
P143350
|
FINISHED |
| Object | Irish |
—
|
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: Irish | Statement: [The Tower of Light, hasLanguageOfNameOrigin, Irish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfNameOrigin Context triple: [The Tower of Light, hasLanguageOfNameOrigin, Irish]
-
A.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
-
B.
hasNameEtymologyIn
chosen
Indicates that the origin or derivation of an entity’s name is based in, or traceable to, a specified source such as a language, place, or cultural context.
-
C.
hasNamesakeLanguage
Indicates that an entity has a language named after it or sharing the same name as the entity.
-
D.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
E.
languageOfNamesake
Indicates the language in which the namesake of an entity (such as a person, place, or object) is named or expressed.
- 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: May 1, 2026, 2 a.m.