Triple
T27165562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscos |
E682772
|
entity |
| Predicate | hasNotableVisitorInFiction |
P142221
|
FINISHED |
| Object | the Stranger |
—
|
NE NERFINISHED |
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: the Stranger | Statement: [Viscos, hasNotableVisitorInFiction, the Stranger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableVisitorInFiction Context triple: [Viscos, hasNotableVisitorInFiction, the Stranger]
-
A.
hasNotableResidentInFiction
Indicates that a place or entity is notably associated with a fictional character who is depicted as residing there.
-
B.
visitedByFictional
chosen
Indicates that a location or place is (in a story or fictional context) visited by a fictional character or entity.
-
C.
hasEventInFiction
Indicates that a fictional work includes or depicts a particular event within its narrative.
-
D.
hasPlaceInFiction
Indicates that a fictional work or element is associated with, set in, or takes place within a particular fictional location or setting.
-
E.
hasViewOfFictional
Indicates that one entity has a visual or conceptual perspective of a fictional entity or scene.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: April 27, 2026, 9:21 a.m.