Triple
T9878313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spaghettii |
E240132
|
entity |
| Predicate | hasArtistApproach |
P10782
|
FINISHED |
| Object | experimental |
—
|
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: experimental | Statement: [Spaghettii, hasArtistApproach, experimental]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtistApproach Context triple: [Spaghettii, hasArtistApproach, experimental]
-
A.
hasArtist
Indicates that an entity (such as a work or item) is associated with or created by a specific artist.
-
B.
hasApproachType
chosen
Indicates the specific method, strategy, or manner in which an action, process, or interaction is carried out or approached.
-
C.
appliesToArtist
Indicates that something (such as a rule, condition, attribute, or action) is relevant or applicable specifically to an artist.
-
D.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
E.
includesApproach
Indicates that one entity incorporates, utilizes, or is characterized by a particular method, strategy, or approach in relation to another entity 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_69ca84e8a0788190b9061811d50fd554 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb4135c108190b3330e929509699d |
completed | April 2, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:37 p.m.