Triple
T32258773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eulerian digraph |
E824091
|
entity |
| Predicate | hasLocalCondition |
P14240
|
FINISHED |
| Object | balance of flow at each vertex |
—
|
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: balance of flow at each vertex | Statement: [Eulerian digraph, hasLocalCondition, balance of flow at each vertex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalCondition Context triple: [Eulerian digraph, hasLocalCondition, balance of flow at each vertex]
-
A.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
B.
localityCondition
chosen
Indicates a spatial or contextual constraint specifying where or under what local conditions a relationship, event, or property holds.
-
C.
hasLocalExpression
Indicates that something has a specific form, representation, or manifestation that is valid or defined only within a particular local context or region.
-
D.
hasChainCondition
Indicates that one entity is subject to, or satisfies, a specified chain condition imposed or characterized by another entity.
-
E.
containsCondition
Indicates that one entity includes, embodies, or is associated with a particular condition.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 1, 2026, 12:41 a.m.