Triple
T11003026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Markov random field |
E260046
|
entity |
| Predicate | oftenDefinedOn |
P4464
|
FINISHED |
| Object | lattice structures |
—
|
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: lattice structures | Statement: [Markov random field, oftenDefinedOn, lattice structures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenDefinedOn Context triple: [Markov random field, oftenDefinedOn, lattice structures]
-
A.
definedOn
chosen
Indicates that something (such as a function, rule, or structure) is specified to apply or be valid over a particular domain, set, or context.
-
B.
areDefinedIn
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
C.
oftenDefines
Indicates that one entity frequently serves to specify, characterize, or determine the nature, meaning, or boundaries of another entity.
-
D.
defined
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
-
E.
endDefinedBy
Indicates that the termination or boundary of one entity is determined, specified, or constrained by 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797546f448190946ee6442d657dc5 |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.