Triple
T8321178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haldane’s dilemma |
E194835
|
entity |
| Predicate | hasBeenAddressedBy |
P16105
|
FINISHED |
| Object | neutral theory of molecular evolution |
—
|
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: neutral theory of molecular evolution | Statement: [Haldane’s dilemma, hasBeenAddressedBy, neutral theory of molecular evolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenAddressedBy Context triple: [Haldane’s dilemma, hasBeenAddressedBy, neutral theory of molecular evolution]
-
A.
addressedBy
chosen
Indicates that something (such as an issue, request, or item) is handled, dealt with, or responded to by a particular agent or entity.
-
B.
addressedThrough
Indicates that an issue, request, or communication is handled, resolved, or processed by means of a specified channel, method, or intermediary.
-
C.
isAddressedTo
Indicates that a message, communication, or item is specifically directed or intended for a particular recipient.
-
D.
hasAddress
Indicates that an entity is associated with a specific address or location.
-
E.
hasSpokenAbout
Indicates that one entity has verbally expressed, discussed, or mentioned another entity or topic.
- 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.