Triple
T8321183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haldane’s dilemma |
E194835
|
entity |
| Predicate | involvesAssumption |
P50642
|
FINISHED |
| Object | hard selection |
—
|
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: hard selection | Statement: [Haldane’s dilemma, involvesAssumption, hard selection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesAssumption Context triple: [Haldane’s dilemma, involvesAssumption, hard selection]
-
A.
isAssumedIn
chosen
Indicates that something is taken for granted or presumed to hold within a particular context, without requiring explicit proof or verification.
-
B.
assumes
Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
-
C.
assumptionOnDomain
Indicates that a particular assumption or constraint is specified to hold over a given domain or set of entities.
-
D.
assumedRuleOf
Indicates that one entity is presumed or taken to hold authoritative control, governance, or dominion over another entity, typically without definitive confirmation.
-
E.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
- 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f67aee88190b245f8d6e57a40b2 |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:55 p.m.