Triple
T36086587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mase’s RichFish Records |
E1043800
|
entity |
| Predicate | labelHead |
P184568
|
FINISHED |
| Object | Mase |
—
|
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: Mase | Statement: [Mase’s RichFish Records, labelHead, Mase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: labelHead Context triple: [Mase’s RichFish Records, labelHead, Mase]
-
A.
labelOf
Indicates that one entity serves as the name, tag, or identifying label assigned to another entity.
-
B.
labelHolders
Indicates that certain entities possess, carry, or are associated with a particular label.
-
C.
titleHolderLabel
Indicates the entity that currently or formerly holds a specified title, position, or honor.
-
D.
headDescription
Indicates that one entity serves as a textual or semantic description of the head (primary) entity in the relationship.
-
E.
headFrom
Indicates a relationship where one entity originates, leads, or directs movement or action from another entity as its starting point or source.
- 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b35e32d481909ef0220e6f6ff4a8 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2c66054819083897e25edb65ba7 |
completed | May 3, 2026, 8:40 p.m. |
Created at: May 3, 2026, 4:08 p.m.