Triple
T13595116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pym Particles |
E324797
|
entity |
| Predicate | inUniverseForm |
P110220
|
FINISHED |
| Object | Gas |
—
|
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: Gas | Statement: [Pym Particles, inUniverseForm, Gas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseForm Context triple: [Pym Particles, inUniverseForm, Gas]
-
A.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
B.
inUniverseMaker
Indicates that an entity exists or occurs within the fictional universe created or defined by another entity.
-
C.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other entity.
-
D.
inUniverseOrigin
Indicates that one entity originates from, or has its source within, the fictional universe or setting defined by another entity.
-
E.
inUniverseActivity
Indicates that an activity or event occurs within the fictional universe or narrative world of a work, rather than outside it (e.g., in real life or meta-context).
- F. None of above. chosen
Provenance (4 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb057f1c881909a3bb77c659a724a |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaf9f3bdc8190838539aaef1f422b |
completed | April 12, 2026, 2:43 p.m. |
Created at: April 9, 2026, 9:49 p.m.