Triple
T28150887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucky Seven Records |
E714616
|
entity |
| Predicate | usedAsReleaseVehicleFor |
P181052
|
FINISHED |
| Object | Madness |
—
|
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: Madness | Statement: [Lucky Seven Records, usedAsReleaseVehicleFor, Madness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsReleaseVehicleFor Context triple: [Lucky Seven Records, usedAsReleaseVehicleFor, Madness]
-
A.
usedAsVehicleFor
Indicates that one entity functions as a means of transportation or conveyance for another entity.
-
B.
hasVehicularUse
Indicates that something is used for, intended for, or associated with operation by vehicles or vehicular traffic.
-
C.
usedChassisFor
Indicates that one entity employed or incorporated another entity’s chassis as the structural base or framework for its construction or operation.
-
D.
usedPoliticalVehicle
Indicates that an entity employed a political organization, campaign, or platform as a means or instrument to achieve its goals or carry out actions.
-
E.
usedForReleaseBy
Indicates that something serves as the means, tool, or mechanism by which another entity is released by a specific agent 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
| PDg | Predicate description generation | batch_69f760a2a90c8190b8fbc55412ab752b |
completed | May 3, 2026, 2:50 p.m. |
Created at: April 27, 2026, 9:59 p.m.