Triple
T24254846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Spaceman |
E603639
|
entity |
| Predicate | associatedWithMemberOfKiss |
P131546
|
FINISHED |
| Object | Ace Frehley |
—
|
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: Ace Frehley | Statement: [The Spaceman, associatedWithMemberOfKiss, Ace Frehley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMemberOfKiss Context triple: [The Spaceman, associatedWithMemberOfKiss, Ace Frehley]
-
A.
hasOnScreenKissWith
Indicates that two entities share a romantic or affectionate kiss depicted visually within the same on-screen scene.
-
B.
associatedBandOfMembers
Indicates a relationship where a specific band is linked to the individual members who belong to or perform in that band.
-
C.
associatedWithBandMemberPersona
chosen
Indicates a relationship where an entity is connected to or linked with the persona or role of a band member.
-
D.
keyMember
Indicates that an entity plays a central, highly important, or leading role within a group, organization, or structure.
-
E.
membershipRecordedBy
Indicates that the recording or documentation of a membership was carried out or created by a specific agent or system.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b8ca4988190b565c2873dc6559d |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:05 a.m.