Triple
T35293373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artaeum |
E1019289
|
entity |
| Predicate | canVanishFrom |
P40090
|
FINISHED |
| Object | Mundus |
—
|
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: Mundus | Statement: [Artaeum, canVanishFrom, Mundus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canVanishFrom Context triple: [Artaeum, canVanishFrom, Mundus]
-
A.
vanishIn
chosen
Indicates that one entity disappears or ceases to be perceptible within, or as part of, another entity or context.
-
B.
vanishesWhen
Indicates that one entity ceases to exist, be visible, or be present whenever a specified condition involving another entity holds.
-
C.
vanishesOn
Indicates that something ceases to exist, be visible, or have effect when it is on or applied to a particular entity or surface.
-
D.
disappearsWith
Indicates that when one entity ceases to exist, is removed, or becomes unavailable, the other entity simultaneously or consequently also ceases to exist, is removed, or becomes unavailable.
-
E.
canBecomeInvisible
Indicates the ability of an entity to transition from being visible to being unseen or undetectable.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7901ae65c819092f17f92d7b2e561 |
completed | May 3, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.