Triple
T35432559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autumn |
E1024101
|
entity |
| Predicate | isModernName |
P182973
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Autumn, isModernName, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isModernName Context triple: [Autumn, isModernName, yes]
-
A.
hasModernName
Indicates that an entity is associated with its current or contemporary name, as opposed to an older or historical one.
-
B.
isModern
Indicates that something belongs to, reflects, or is characteristic of the contemporary or recent period, especially in style, design, or thinking.
-
C.
hasModernNamesake
Indicates that an entity is the namesake or inspiration for a modern entity that shares or derives its name from it.
-
D.
isModernFormOf
Indicates that one entity is a newer or contemporary version, adaptation, or evolution of another earlier entity.
-
E.
hasModernNameLanguage
Indicates that the modern name of an entity is expressed in a particular language.
- F. None of above. chosen
Provenance (4 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_69f76df743c48190aecb6dd79efb0d95 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f795b7d77081909bb1be08edf5adef |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 3, 2026, 4:03 p.m.