Triple
T16367924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Correspondência de Fradique Mendes |
E397483
|
entity |
| Predicate | fictionalDevice |
P84710
|
FINISHED |
| Object | imaginary correspondence |
—
|
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: imaginary correspondence | Statement: [Correspondência de Fradique Mendes, fictionalDevice, imaginary correspondence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalDevice Context triple: [Correspondência de Fradique Mendes, fictionalDevice, imaginary correspondence]
-
A.
fictionalObject
chosen
Indicates that one entity is a fictional or imaginary object in relation to another entity.
-
B.
fictionalUse
Indicates that one entity makes use of another within a fictional or imaginary context, rather than in real-world usage.
-
C.
hasFictionalFunction
Indicates that an entity serves a role, purpose, or function within a fictional context or narrative.
-
D.
fictionalSon
Indicates that one entity is portrayed as the son of another entity within a fictional or narrative context.
-
E.
featuresFictionalTechnology
Indicates that an entity includes, depicts, or makes use of imagined or speculative technology that does not exist in reality.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2ff3f0694819097faa1c1447a9e97 |
completed | April 18, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.