Triple
T30521114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infront Motor Sports |
E776694
|
entity |
| Predicate | organizationalRoleInSBK |
P180643
|
FINISHED |
| Object | calendar planning |
—
|
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: calendar planning | Statement: [Infront Motor Sports, organizationalRoleInSBK, calendar planning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizationalRoleInSBK Context triple: [Infront Motor Sports, organizationalRoleInSBK, calendar planning]
-
A.
hasOrganizationalRole
Indicates that an entity holds a specific role, position, or function within an organization.
-
B.
basisRole
Indicates that one role serves as the foundational or underlying role upon which another role or function is defined or derived.
-
C.
awardingOrganizationRole
Indicates that an entity holds a specific role or capacity within the organization that grants or confers an award.
-
D.
roleAtSKIMS
Indicates that an entity holds or held a specific role or position at the institution SKIMS.
-
E.
roleAtSiebelSystems
Indicates that an entity held a specific role or position at Siebel Systems.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 29, 2026, 8:17 p.m.