Triple
T14260609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaywalking |
E353505
|
entity |
| Predicate | hasPresenterRole |
P26905
|
FINISHED |
| Object | interviewer |
—
|
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: interviewer | Statement: [Jaywalking, hasPresenterRole, interviewer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPresenterRole Context triple: [Jaywalking, hasPresenterRole, interviewer]
-
A.
hasPresenterType
chosen
Indicates the specific role or category of presenter associated with an event, item, or presentation.
-
B.
hasPresentation
Indicates that an entity delivers, contains, or is associated with a specific presentation (such as a talk, slide deck, or formal display of information).
-
C.
hasStageRole
Indicates that an entity performs or holds a specific role or character in a staged performance or theatrical production.
-
D.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
E.
hasJudgesRole
Indicates that an entity serves in the capacity or role of a judge within a specified context 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de635534988190816fdfb315cd2a3f |
completed | April 14, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:09 a.m.