Triple
T19535880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lane Boy |
E488764
|
entity |
| Predicate | hasRockInfluence |
P127455
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lane Boy, hasRockInfluence, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRockInfluence Context triple: [Lane Boy, hasRockInfluence, true]
-
A.
usesMusicalInfluence
chosen
Indicates that one entity draws upon, incorporates, or is guided by the musical style, ideas, or legacy of another entity in its own musical creation or expression.
-
B.
hasRockSubgenre
Indicates a relationship where one musical style is classified as a subgenre within the broader category of rock music.
-
C.
hasGenreInfluenceOn
Indicates that one genre has a notable impact on shaping or influencing the characteristics, style, or development of another genre.
-
D.
hasRockRecord
Indicates that an entity possesses or is associated with a documented record related to rock music or rock materials.
-
E.
influencesMusicOf
Indicates that one entity has an effect on, shapes, or contributes to the musical style, content, or development of another entity.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6386f0fac819081bbc29172c8965e |
completed | April 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.