Triple
T23435781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Night in Venice boat parade |
E563455
|
entity |
| Predicate | audienceViewpoints |
P144939
|
FINISHED |
| Object | bayfront homes |
—
|
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: bayfront homes | Statement: [Night in Venice boat parade, audienceViewpoints, bayfront homes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceViewpoints Context triple: [Night in Venice boat parade, audienceViewpoints, bayfront homes]
-
A.
audienceImpact
Indicates how an action, message, or event affects, influences, or resonates with its intended audience.
-
B.
popularViewpointFor
Indicates that a particular viewpoint is widely held or commonly accepted within a specified group, context, or domain.
-
C.
audienceScale
Indicates the relative size or reach of the audience associated with an entity, event, or communication.
-
D.
exploresPerspectiveOf
chosen
Indicates that one entity examines, investigates, or considers the viewpoint, stance, or outlook associated with another entity.
-
E.
toldFromMultipleViewpoints
Indicates that the same event or narrative is recounted from more than one character’s or observer’s perspective.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5dbdf248190a09e971f2718d01f |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:50 p.m.