Triple
T30369344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | transition network |
E772507
|
entity |
| Predicate | edgeLabeledBy |
P88300
|
FINISHED |
| Object | input symbols |
—
|
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: input symbols | Statement: [transition network, edgeLabeledBy, input symbols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: edgeLabeledBy Context triple: [transition network, edgeLabeledBy, input symbols]
-
A.
edgeType
Indicates the specific kind or category of connection that exists between two related entities.
-
B.
edgeFeature
Indicates a characteristic or property specifically associated with an edge or boundary within a structure, graph, or spatial configuration.
-
C.
edgeWeights
Indicates a relationship where each edge in a graph is associated with a specific numerical weight or cost.
-
D.
namedOnEdge
chosen
Indicates that a name or label is assigned specifically to an edge (a connection or relationship) rather than to the nodes it links.
-
E.
edgeTransitivity
Indicates how consistently connections between entities form transitive patterns, such that if one entity is linked to a second and the second to a third, there is also a direct link between the first and third.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682825f408190b6510f20015c4e52 |
completed | May 2, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:59 p.m.