Triple
T33598528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jadis |
E860643
|
entity |
| Predicate | laterLanguageStyle |
P115652
|
FINISHED |
| Object | more conventional English (as Anne) |
—
|
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: more conventional English (as Anne) | Statement: [Jadis, laterLanguageStyle, more conventional English (as Anne)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterLanguageStyle Context triple: [Jadis, laterLanguageStyle, more conventional English (as Anne)]
-
A.
styleLanguage
Indicates a relationship where one entity specifies the language or linguistic style in which another entity is expressed, formatted, or presented.
-
B.
laterTraditionsLanguage
chosen
Indicates that later traditions or sources refer to or describe the subject using the specified language.
-
C.
stylisticRange
Indicates the range or spectrum of styles that characterize or can be applied to something.
-
D.
laterLanguageOfServices
Indicates that one language is used for services at a later time or stage than another language.
-
E.
suffixLanguage
Indicates that one language is used as a suffix or ending element in the formation or representation of another language or linguistic expression.
- 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fff09dae088190bd8460060d778feb |
completed | May 10, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69fff0027c5c8190baa5c7a15852cbe0 |
completed | May 10, 2026, 2:40 a.m. |
Created at: May 1, 2026, 1:41 a.m.