Triple
T3145488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gundersen method |
E65752
|
entity |
| Predicate | usedInEventType |
P38977
|
FINISHED |
| Object | individual Nordic combined events |
—
|
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: individual Nordic combined events | Statement: [Gundersen method, usedInEventType, individual Nordic combined events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInEventType Context triple: [Gundersen method, usedInEventType, individual Nordic combined events]
-
A.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
B.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
C.
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.
-
D.
associatedEventType
chosen
Indicates that one entity is linked to another by the type or category of event with which it is associated.
-
E.
eventUsage
Indicates how an event is employed, applied, or utilized within a particular context or process.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada59797788190a8d71262888c5df0 |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfa3d9081908425aa636bb9b897 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.