Triple
T16561619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Primavera |
E402351
|
entity |
| Predicate | nicknameEmphasises |
P39779
|
FINISHED |
| Object | springtime scheduling |
—
|
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: springtime scheduling | Statement: [La Primavera, nicknameEmphasises, springtime scheduling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameEmphasises Context triple: [La Primavera, nicknameEmphasises, springtime scheduling]
-
A.
nicknameEmphasizes
chosen
Indicates that a nickname highlights or draws special attention to a particular characteristic, trait, or aspect of the entity it refers to.
-
B.
nicknameCategory
Indicates that one entity is a nickname and the other entity is the category or type that this nickname belongs to.
-
C.
nicknamePattern
Indicates that one entity serves as a nickname or informal name pattern for another entity.
-
D.
nicknameForRole
Indicates that one entity is an informal or alternative name commonly used to refer to a particular role or position represented by another entity.
-
E.
nickNameGivenBy
Indicates that one entity assigns or uses a particular nickname for another entity.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3576eb63081908cb5dc6c0a8a13ac |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.