Triple
T29072248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ehrenfest model |
E735840
|
entity |
| Predicate | transitionGraph |
P193472
|
FINISHED |
| Object | birth–death chain |
—
|
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: birth–death chain | Statement: [Ehrenfest model, transitionGraph, birth–death chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitionGraph Context triple: [Ehrenfest model, transitionGraph, birth–death chain]
-
A.
transitionState
Indicates a change in condition or phase from one defined state to another within a process or system.
-
B.
transitionFunctionType
Indicates the type or category of a state-transition function that governs how a system moves from one state to another.
-
C.
transitionProgram
Indicates a relationship where one entity serves as a program or structured process that facilitates another entity’s transition from one state, phase, or condition to another.
-
D.
transitionCharacteristic
Indicates a relationship where an entity is characterized by how it changes state or condition over time or between phases.
-
E.
transition
Indicates a change of state or condition from one form, phase, or situation to another.
- F. None of above. chosen
Provenance (4 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69fd485e0c20819099756b4fe39ac326 |
completed | May 8, 2026, 2:20 a.m. |
Created at: April 28, 2026, 10:20 a.m.