Triple
T35209700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Masters of Atlantis |
E1016638
|
entity |
| Predicate | hasFictionalText |
P197301
|
FINISHED |
| Object | Codex Pappus |
—
|
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: Codex Pappus | Statement: [Masters of Atlantis, hasFictionalText, Codex Pappus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalText Context triple: [Masters of Atlantis, hasFictionalText, Codex Pappus]
-
A.
hasFictionalContent
Indicates that something contains or includes material that is imaginary, invented, or not intended to represent real events or facts.
-
B.
hasFictionalDocument
chosen
Indicates that one entity possesses, is associated with, or includes a document that is fictional or exists only within an imagined or narrative context.
-
C.
hasFictionalType
Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
-
D.
hasFictionalSignText
Indicates that an entity bears or is associated with text appearing on a fictional sign (e.g., wording depicted on an in-universe sign).
-
E.
hasFictionalForm
Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary context.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
Created at: May 3, 2026, 4:02 p.m.