Triple
T27661854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eventarc |
E697143
|
entity |
| Predicate | routesEventsTo |
P165394
|
FINISHED |
| Object | Cloud Run |
—
|
NE NERFINISHED |
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: Cloud Run | Statement: [Eventarc, routesEventsTo, Cloud Run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routesEventsTo Context triple: [Eventarc, routesEventsTo, Cloud Run]
-
A.
routeOrganized
Indicates that an entity has arranged or structured a specific route or path according to some plan or criteria.
-
B.
recordsEventsVia
Indicates that one entity captures or logs events through the mechanism, system, or medium provided by another entity.
-
C.
mainEventFor
Indicates that one event is the primary or central event associated with another entity, such as a context, grouping, or larger occurrence.
-
D.
routingBasis
Indicates the principle or criterion used to determine how something is directed, routed, or assigned among possible paths or destinations.
-
E.
routeDiscovered
Indicates that a path or connection between two locations or nodes has been successfully found or identified.
- F. None of above. chosen
Provenance (4 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 27, 2026, 2:36 p.m.