Triple
T35325366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. van Pelt |
E1020165
|
entity |
| Predicate | visibilityInSeries |
P183013
|
FINISHED |
| Object | rarely seen |
—
|
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: rarely seen | Statement: [Mr. van Pelt, visibilityInSeries, rarely seen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibilityInSeries Context triple: [Mr. van Pelt, visibilityInSeries, rarely seen]
-
A.
situatedInSeries
Indicates that one entity is located or positioned within a particular series, sequence, or ordered collection of related items.
-
B.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
C.
basedInSeries
Indicates that one entity is set, located, or primarily takes place within the narrative world or context of a particular series.
-
D.
appearsInSeriesBy
Indicates that one entity (such as a work or character) is featured within a series that is created, authored, or produced by another entity.
-
E.
visibleBy
Indicates that one entity can be seen or perceived visually 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f795b5228c8190adb5bf86e581f70c |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f79527c7bc8190a69d87bec01f65c8 |
completed | May 3, 2026, 6:34 p.m. |
Created at: May 3, 2026, 4:03 p.m.