Triple
T31521538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J-o-n-t-y |
E804218
|
entity |
| Predicate | stylizedFormOf |
P137145
|
FINISHED |
| Object | Jonty |
—
|
NE NERFINISHED |
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: Jonty | Statement: [J-o-n-t-y, stylizedFormOf, Jonty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stylizedFormOf Context triple: [J-o-n-t-y, stylizedFormOf, Jonty]
-
A.
standardizedFormOf
Indicates that one entity is the normalized or officially standardized version of another, often consolidating variations or alternative forms into a single canonical form.
-
B.
standardFormUsedIn
Indicates that a particular standard form is employed or applied within a given context, process, or system.
-
C.
formedStable
Indicates that a relationship, structure, or configuration has come into existence and remains consistently intact or unchanged over time.
-
D.
stylisticElement
chosen
Indicates a relationship where one entity functions as a stylistic feature, device, or characteristic that shapes the expressive or aesthetic quality of another entity.
-
E.
isTraditionalFormOf
Indicates that one entity is the historically established or customary version from which another, typically more modern or variant, form is derived.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:56 p.m.