Triple
T10040528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Here Comes My Man |
E205282
|
entity |
| Predicate | followsWorkType |
P86785
|
FINISHED |
| Object | single |
—
|
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: single | Statement: [Here Comes My Man, followsWorkType, single]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsWorkType Context triple: [Here Comes My Man, followsWorkType, single]
-
A.
followsWork
Indicates that one work (such as a publication, version, or creative piece) comes directly after another in sequence or succession.
-
B.
associatedWorkType
chosen
Indicates the type or category of work with which an entity is associated (e.g., publication, artwork, performance).
-
C.
originallyFromWorkType
Indicates that one entity was derived, adapted, or sourced from an original work of a specified type (e.g., book, film, artwork).
-
D.
associatedWithWorkOf
Indicates that one entity has a connection or involvement with the work, creation, or output produced by another entity.
-
E.
appliesToWork
Indicates that something (such as a rule, policy, condition, or attribute) is relevant to, governs, or is in effect for a particular piece of work or work-related activity.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcee2e6d881908cfa0579f9be32e4 |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:55 p.m.