Triple
T32565480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Papadapolis |
E832350
|
entity |
| Predicate | familyNameOriginInFiction |
P29280
|
FINISHED |
| Object | Greek |
—
|
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: Greek | Statement: [George Papadapolis, familyNameOriginInFiction, Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyNameOriginInFiction Context triple: [George Papadapolis, familyNameOriginInFiction, Greek]
-
A.
hasFamilyNameInFiction
Indicates that a fictional character is associated with a particular family name within a work of fiction.
-
B.
usedAsFictionalCharacterSurname
chosen
Indicates that a surname is employed as the last name of a fictional character in a narrative work.
-
C.
characterNameOrigin
Indicates the source or inspiration from which a character’s name is derived.
-
D.
familySurnameInStory
Indicates that a particular family surname appears within the narrative or context of a given story.
-
E.
ownerRealNameInFiction
Indicates that a fictional work reveals or uses the real-world name of the owner of a referenced entity within the story.
- 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_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:03 a.m.