Triple
T26008326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeffrey Maier |
E646820
|
entity |
| Predicate | hasLifelongInterestIn |
P66206
|
FINISHED |
| Object | baseball |
—
|
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: baseball | Statement: [Jeffrey Maier, hasLifelongInterestIn, baseball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLifelongInterestIn Context triple: [Jeffrey Maier, hasLifelongInterestIn, baseball]
-
A.
subjectInterest
chosen
Indicates that the subject has an interest in, or is concerned with, the object.
-
B.
primaryInterest
Indicates that one entity is the main or most significant focus of attention, concern, or engagement for another entity.
-
C.
hasPetInterest
Indicates that one entity has an interest in, affinity for, or concern about pets in relation to another entity or context.
-
D.
hasInterestType
Indicates that an entity is associated with a specific category or type of interest it holds or is concerned with.
-
E.
hasSpiritualInterestIn
Indicates a relationship where one entity is spiritually drawn to, concerned with, or engaged in the religious or metaphysical aspects of another entity.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 22, 2026, 9:01 a.m.