Triple
T35016935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon & Marcy |
E1010078
|
entity |
| Predicate | exploresSetting |
P32516
|
FINISHED |
| Object | post-apocalyptic Earth |
—
|
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: post-apocalyptic Earth | Statement: [Simon & Marcy, exploresSetting, post-apocalyptic Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploresSetting Context triple: [Simon & Marcy, exploresSetting, post-apocalyptic Earth]
-
A.
exploresFor
Indicates that one entity actively investigates or searches within or on behalf of another entity, typically to discover or obtain something for that other entity’s benefit.
-
B.
featuresSetting
chosen
Indicates that something includes, presents, or highlights a particular setting as a notable or primary aspect.
-
C.
coversSetting
Indicates that one entity includes or addresses a particular setting or context within its scope.
-
D.
explores
Indicates actively investigating, traveling through, or examining something in order to discover or learn more about it.
-
E.
explorationUse
Indicates the use of something specifically for exploration or investigative activities.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:01 p.m.