Triple
T26589103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Soul Man |
E667295
|
entity |
| Predicate | hasPilotAs |
P161586
|
FINISHED |
| Object | backdoor pilot on Hot in Cleveland |
—
|
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: backdoor pilot on Hot in Cleveland | Statement: [The Soul Man, hasPilotAs, backdoor pilot on Hot in Cleveland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPilotAs Context triple: [The Soul Man, hasPilotAs, backdoor pilot on Hot in Cleveland]
-
A.
hasPilot
Indicates that an entity is operated or controlled by a specific pilot.
-
B.
hasPilotType
Indicates that an entity has or is associated with a specific type or category of pilot.
-
C.
hasPilotStatus
Indicates that an entity holds or is assigned a specific pilot-related status or role.
-
D.
hasPilotOnboard
Indicates that a vehicle or craft currently has a pilot physically present and onboard.
-
E.
hasPilotage
Indicates a relationship where one entity provides or is subject to navigational guidance or piloting services by another entity.
- 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_69ee9cfb7e548190b60a9031182f5a7e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61ad613608190855de13501a86007 |
completed | May 2, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f61a16b7848190bf20d2be7e5a16c1 |
completed | May 2, 2026, 3:36 p.m. |
Created at: April 27, 2026, 2:07 a.m.