Triple
T37921582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WDVX Blue Plate Special |
E945977
|
entity |
| Predicate | hasInPersonAttendance |
P65012
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [WDVX Blue Plate Special, hasInPersonAttendance, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInPersonAttendance Context triple: [WDVX Blue Plate Special, hasInPersonAttendance, yes]
-
A.
hasPhysicalPresence
Indicates that an entity exists or manifests in a tangible, spatially located form within the physical world.
-
B.
hasAttended
Indicates that an entity has been present at or participated in a particular event, place, or gathering.
-
C.
hasAttendanceType
chosen
Indicates the specific category or mode of attendance associated with an event or participant (e.g., in-person, virtual, hybrid).
-
D.
hasInPersonVoting
Indicates that an election or decision-making process includes the option for participants to cast their votes physically at a designated location.
-
E.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a013f09b0988190ba3179c7d56c726a |
completed | May 11, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_6a013e600e248190a1a9c363702c8586 |
completed | May 11, 2026, 2:26 a.m. |
Created at: May 3, 2026, 4:20 p.m.