Triple
T30303818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geographical Fugue |
E770723
|
entity |
| Predicate | EnglishTextAdapter |
P165939
|
FINISHED |
| Object | unknown |
—
|
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: unknown | Statement: [Geographical Fugue, EnglishTextAdapter, unknown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EnglishTextAdapter Context triple: [Geographical Fugue, EnglishTextAdapter, unknown]
-
A.
EnglishTranslation
Indicates that one expression is the English-language translation equivalent of another expression.
-
B.
EnglishTranslatorOfWork
Indicates that one entity is the person who translated a specific work into English.
-
C.
textTranslation
Indicates a relationship where one text is rendered into another language or form while preserving its original meaning.
-
D.
textAdapter
chosen
Indicates a relationship where one entity converts, formats, or adapts text from one form or context to another for use by a different component or system.
-
E.
EnglishVersionFeature
Indicates that the related item is a feature or aspect specifically associated with the English-language version of something.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68166930881909608eece2bc5f055 |
completed | May 2, 2026, 10:57 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:49 p.m.