Triple
T7678215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godunov-type schemes |
E173919
|
entity |
| Predicate | typicalGrid |
P24732
|
FINISHED |
| Object | structured grids |
—
|
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: structured grids | Statement: [Godunov-type schemes, typicalGrid, structured grids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGrid Context triple: [Godunov-type schemes, typicalGrid, structured grids]
-
A.
gridType
chosen
Indicates the specific structural or organizational pattern of a grid used to arrange or reference elements.
-
B.
typicalTopology
Indicates the usual or most common network or structural arrangement that characterizes how the related entities are organized or interconnected.
-
C.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
D.
regulatesGridThrough
Indicates that one entity controls or influences the operation or behavior of an electrical grid by means of another specified intermediary or mechanism.
-
E.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
- 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_69c6995703e0819081de77361b602e78 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4:01 p.m.