Triple
T10767177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lake Isle of Innisfree |
E253982
|
entity |
| Predicate | hasFamousStatus |
P27257
|
FINISHED |
| Object | one of Yeats's most popular poems |
—
|
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: one of Yeats's most popular poems | Statement: [The Lake Isle of Innisfree, hasFamousStatus, one of Yeats's most popular poems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamousStatus Context triple: [The Lake Isle of Innisfree, hasFamousStatus, one of Yeats's most popular poems]
-
A.
fameStatus
chosen
Indicates the level or state of public recognition or renown associated with an entity.
-
B.
hasFamousSection
Indicates that an entity includes or contains a part, area, or segment that is widely recognized or renowned.
-
C.
hasFamousPage
Indicates that an entity is associated with a well-known or widely recognized page, such as on a website or platform.
-
D.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
E.
hasIconicStatus
Indicates that an entity holds a widely recognized, emblematic, or culturally significant status within a particular domain or context.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d7322eb2f08190999e09428e7f7ba8 |
completed | April 9, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.