Triple
T27947246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curriculum Vitae |
E703316
|
entity |
| Predicate | isAReleaseOf |
P163802
|
FINISHED |
| Object | Mo' Hits Records |
—
|
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: Mo' Hits Records | Statement: [Curriculum Vitae, isAReleaseOf, Mo' Hits Records]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAReleaseOf Context triple: [Curriculum Vitae, isAReleaseOf, Mo' Hits Records]
-
A.
isOfficialReleaseOf
Indicates that one entity is the formally authorized, final, and publicly distributed version of another entity (such as a product, work, or software).
-
B.
isVersionOf
Indicates that one entity is a particular version, edition, or variant derived from another entity.
-
C.
isSoloReleaseOf
Indicates that a release is a solo work attributed to a single primary artist, rather than a group or collaboration, for a given musical entity.
-
D.
isInternalVersionOf
Indicates that one entity is an internal or non-public variant, edition, or build of another entity.
-
E.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63c045bd081908e0cb2a119202e8f |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63b3039808190b00bbd19161487f3 |
completed | May 2, 2026, 5:58 p.m. |
Created at: April 27, 2026, 7:23 p.m.