Triple
T31049653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | These Are My Songs |
E791223
|
entity |
| Predicate | sideOneIncludes |
P1393
|
FINISHED |
| Object | This Is My Song |
—
|
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: This Is My Song | Statement: [These Are My Songs, sideOneIncludes, This Is My Song]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideOneIncludes Context triple: [These Are My Songs, sideOneIncludes, This Is My Song]
-
A.
sideOneStructure
Indicates that the specified structure is located on or associated with the first (designated "one") side of a bilateral or two-sided entity or relationship.
-
B.
singleSideOf
Indicates that one entity constitutes a single side or face of another entity, typically within a larger multi-sided structure or object.
-
C.
seriesIncludes
Indicates that a particular series contains or encompasses the referenced item as one of its constituent parts.
-
D.
includes
chosen
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
E.
includedOnSingle
Indicates that something is contained or listed within exactly one specific item, set, or context, and not in any others.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953eb0d4819098ac02bd7a53f3b8 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9 p.m.