Triple
T4923529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John McGuinness |
E110520
|
entity |
| Predicate | isActiveIn |
P50824
|
FINISHED |
| Object | 21st-century motorcycle racing |
—
|
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: 21st-century motorcycle racing | Statement: [John McGuinness, isActiveIn, 21st-century motorcycle racing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isActiveIn Context triple: [John McGuinness, isActiveIn, 21st-century motorcycle racing]
-
A.
isActive
Indicates that an entity is currently functioning, engaged, or enabled within a given context or system.
-
B.
isPotentiallyActive
Indicates that an entity has the capacity or conditions to become active, but is not necessarily active at the present moment.
-
C.
activeInEvent
chosen
Indicates that an entity participates in or is involved in carrying out actions within a particular event.
-
D.
activeFrom
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
E.
activeInFieldFrom
Indicates that an entity is professionally or actively engaged in a particular field starting from a specified point in time.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffd46748190843fed99f02fd8d5 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3695c8819094e7ad2f6d4ba1ac |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.