Triple
T38359044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingwe |
E1046418
|
entity |
| Predicate | hasNotabilityAmong |
P156150
|
FINISHED |
| Object | racing enthusiasts |
—
|
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: racing enthusiasts | Statement: [Ingwe, hasNotabilityAmong, racing enthusiasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotabilityAmong Context triple: [Ingwe, hasNotabilityAmong, racing enthusiasts]
-
A.
hasNotabilityFor
chosen
Indicates that an entity is notable, recognized, or significant specifically in relation to a given subject, context, or domain.
-
B.
hasNotabilityLevel
Indicates that an entity possesses a specified degree or rank of prominence, importance, or recognition relative to others.
-
C.
hasNotabilityBasis
Indicates that the notability or significance of one entity is based on, or derived from, another entity or factor.
-
D.
hasNotabilityNote
Indicates that there is an associated note or annotation explaining the significance, prominence, or special relevance of the subject.
-
E.
hasNotabilityCategory
Indicates that an entity is associated with a particular category that characterizes its type or area of notability.
- 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_69f76e3a94fc81908edc175e8d259e80 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.