Triple
T34711441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maxwell’s demon |
E1000655
|
entity |
| Predicate | resolutionProposedBy |
P70395
|
FINISHED |
| Object | Leo Szilard |
—
|
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: Leo Szilard | Statement: [Maxwell’s demon, resolutionProposedBy, Leo Szilard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resolutionProposedBy Context triple: [Maxwell’s demon, resolutionProposedBy, Leo Szilard]
-
A.
resolutionOf
Indicates that one entity is the formal decision, outcome, or solution produced in response to, or for the purpose of addressing, another entity such as an issue, proposal, or problem.
-
B.
resolution
Indicates the act of formally deciding, settling, or expressing a determined stance on an issue, often through an official decision or statement.
-
C.
resolutionType
Indicates the specific manner or category by which an issue, event, or conflict is resolved or brought to a conclusion.
-
D.
resolutionIdea
Indicates a proposed method, plan, or approach intended to resolve or address a particular issue, conflict, or problem.
-
E.
hasProposedResolution
chosen
Indicates that an entity has put forward a specific resolution or solution for consideration or decision regarding another entity or issue.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.