Triple
T8912987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | shifting balance theory |
E212228
|
entity |
| Predicate | describesInteractionOf |
P264
|
FINISHED |
| Object | genetic drift |
—
|
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: genetic drift | Statement: [shifting balance theory, describesInteractionOf, genetic drift]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesInteractionOf Context triple: [shifting balance theory, describesInteractionOf, genetic drift]
-
A.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
B.
describes
chosen
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
C.
selfInteracts
Indicates that an entity interacts with itself, rather than with a distinct external entity.
-
D.
notablePropInteraction
Indicates a significant or noteworthy interaction or relationship occurring between the specified entities.
-
E.
interactionMechanism
Indicates the process or means by which one entity affects, influences, or interacts with another.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6525d1408190a76522d7c4ac37da |
completed | April 1, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.