Triple
T5452312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyber Rodeo |
E122396
|
entity |
| Predicate | eventScale |
P64403
|
FINISHED |
| Object | large-scale |
—
|
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: large-scale | Statement: [Cyber Rodeo, eventScale, large-scale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventScale Context triple: [Cyber Rodeo, eventScale, large-scale]
-
A.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
-
B.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
C.
eventName
Indicates the specific label or title assigned to identify an event within a system or context.
-
D.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
E.
eventFocus
Indicates that a particular event is the primary subject of attention, analysis, or relevance within a given context or dataset.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
| PDg | Predicate description generation | batch_69bd95bd53f48190a03144beb290f2cb |
completed | March 20, 2026, 6:45 p.m. |
Created at: March 20, 2026, 2:08 p.m.