Triple
T32565472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Papadapolis |
E832350
|
entity |
| Predicate | activeInFictionalUniverseDuring |
P107311
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [George Papadapolis, activeInFictionalUniverseDuring, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeInFictionalUniverseDuring Context triple: [George Papadapolis, activeInFictionalUniverseDuring, 1980s]
-
A.
activeInFictionalUniverse
Indicates that an entity participates, operates, or has a role within a specified fictional universe or setting.
-
B.
activeInFictionalYear
chosen
Indicates that an entity is active or operating during a specified fictional or imaginary year within a narrative or fictional timeline.
-
C.
isSetInFictionalUniverse
Indicates that a narrative work takes place within a specific fictional universe or setting.
-
D.
hasFictionalUniverseElement
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
E.
livesInFiction
Indicates that one entity exists or resides within the fictional world or narrative setting created by another entity.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 1, 2026, 1:03 a.m.