Triple
T11084506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Markov semigroup |
E262082
|
entity |
| Predicate | generatorCalled |
P40691
|
FINISHED |
| Object | Markov generator |
—
|
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: Markov generator | Statement: [Markov semigroup, generatorCalled, Markov generator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generatorCalled Context triple: [Markov semigroup, generatorCalled, Markov generator]
-
A.
hasGeneratingFunction
Indicates that one entity serves as the generating function associated with, or defining, another entity.
-
B.
generationMethod
Indicates the process, technique, or procedure by which something is created, produced, or derived.
-
C.
calledAs
chosen
Indicates that one entity is referred to, named, or addressed by another specific name or label.
-
D.
generationCount
Indicates the number of times a process, entity, or version has been created, iterated, or regenerated within a sequence or lifecycle.
-
E.
holderCalled
Indicates that one entity, acting as a holder or possessor, initiated a phone call or communication to another entity.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799c0cc3081908448cfb26c08daf5 |
completed | April 9, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.