Triple
T33540038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dolphins |
E859044
|
entity |
| Predicate | hasStrokeSpecialization |
P44440
|
FINISHED |
| Object | freestyle |
—
|
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: freestyle | Statement: [The Dolphins, hasStrokeSpecialization, freestyle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrokeSpecialization Context triple: [The Dolphins, hasStrokeSpecialization, freestyle]
-
A.
hasStrokeType
chosen
Indicates that an entity is associated with a specific type or classification of stroke.
-
B.
hasStrokeContrast
Indicates that the thickness of a character’s strokes varies, distinguishing it from designs with uniform stroke weight.
-
C.
isStrokeStyleType
Indicates that one entity is classified as a particular type or category of stroke style in a drawing or graphics context.
-
D.
hasSpecial
Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
-
E.
hasStrokeOrder
Indicates that there is a specific, ordered sequence of strokes used to write or draw the related symbol or character.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff4fc6077c8190b8fd9b43fcfde986 |
completed | May 9, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69ff4e61fb648190a72f7918961ece9c |
completed | May 9, 2026, 3:10 p.m. |
Created at: May 1, 2026, 1:39 a.m.