Triple
T2373485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Markov chain Monte Carlo |
E46140
|
entity |
| Predicate | originatedInField |
P3654
|
FINISHED |
| Object | statistical physics |
—
|
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: statistical physics | Statement: [Markov chain Monte Carlo, originatedInField, statistical physics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatedInField Context triple: [Markov chain Monte Carlo, originatedInField, statistical physics]
-
A.
originatedInCourt
Indicates that a legal case, decision, or proceeding began or was first filed in a specified court.
-
B.
formerField
Indicates that an entity previously had a particular field, role, or area of activity, but no longer does.
-
C.
originallyIn
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
-
D.
hasOriginIn
chosen
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
E.
developedInField
Indicates that an entity (such as a method, theory, or technology) was created, formulated, or advanced within a particular academic or professional field.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abca4d89248190be7d712d5fa8382b |
completed | March 7, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69abc59d82f08190b7c36982d1ae783d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.