Triple
T22125923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitchie Torres |
E546789
|
entity |
| Predicate | secondaryTalent |
P117399
|
FINISHED |
| Object | songwriting |
—
|
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: songwriting | Statement: [Mitchie Torres, secondaryTalent, songwriting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryTalent Context triple: [Mitchie Torres, secondaryTalent, songwriting]
-
A.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
B.
secondaryInterest
chosen
Indicates that an entity has a secondary, less primary but still relevant interest or focus in relation to another entity or topic.
-
C.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
D.
secondaryDiscipline
Indicates that an entity has an additional, subordinate field of study or area of specialization associated with it, distinct from its primary discipline.
-
E.
secondaryStrength
Indicates a secondary or supporting level of strength or influence that complements a primary one in the relationship between entities.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12981ac008190aafb516f2a28fefc |
completed | April 28, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.