Triple
T36341837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Who (Sunny song) |
E894944
|
entity |
| Predicate | hasTitleCharacterCount |
P196194
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Who (Sunny song), hasTitleCharacterCount, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleCharacterCount Context triple: [Who (Sunny song), hasTitleCharacterCount, 3]
-
A.
hasTitleCharacterFrom
Indicates that a work has a title that includes or is derived from a specific character.
-
B.
hasTitleLetter
Indicates that an entity possesses a specific letter or character within its title.
-
C.
hasTitleCharacterInContext
Indicates that a particular character appears in the title of an entity when considered within a specific contextual setting or scope.
-
D.
hasTitleName
Indicates that an entity possesses or is associated with a specific title or name.
-
E.
isTitleCharacterString
Indicates that a given string represents the title text associated with an entity.
- 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_69f76e4e90148190b02fe52593c70b5b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
| PDg | Predicate description generation | batch_69fe12a769c08190bc445d302d2e8f98 |
completed | May 8, 2026, 4:43 p.m. |
Created at: May 3, 2026, 4:09 p.m.