Triple
T10034603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joseph Schwartz |
E204933
|
entity |
| Predicate | settingWorldStatus |
P53413
|
FINISHED |
| Object | Earth is a radioactive backwater |
—
|
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: Earth is a radioactive backwater | Statement: [Joseph Schwartz, settingWorldStatus, Earth is a radioactive backwater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingWorldStatus Context triple: [Joseph Schwartz, settingWorldStatus, Earth is a radioactive backwater]
-
A.
stateSetting
chosen
Indicates that one entity establishes, configures, or assigns the state or condition of another entity.
-
B.
globalStatus
Indicates the overall state or condition of an entity as evaluated at a system-wide or global level.
-
C.
settingControlled
Indicates that one entity regulates, adjusts, or determines the configuration or parameters of another entity.
-
D.
hasWorld
Indicates that an entity possesses, is associated with, or encompasses a particular world or global context.
-
E.
controlStatus
Indicates that one entity has a particular level, state, or condition of control over another entity or process.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdce4a515c8190baec86d924623b12 |
completed | April 2, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:54 p.m.