Triple
T15718793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bobby Elvis |
E381030
|
entity |
| Predicate | hasClubPatch |
P119905
|
FINISHED |
| Object | Reaper patch |
—
|
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: Reaper patch | Statement: [Bobby Elvis, hasClubPatch, Reaper patch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClubPatch Context triple: [Bobby Elvis, hasClubPatch, Reaper patch]
-
A.
hasClub
Indicates that an entity is associated with or belongs to a particular club.
-
B.
appliesToClub
Indicates that something (such as a rule, policy, attribute, or action) is relevant or applicable specifically to a particular club.
-
C.
replacedClub
Indicates that one club has taken the place of another club, typically succeeding it in role, position, or membership.
-
D.
hasHomeClub
Indicates that an entity (typically a person, such as an athlete) is associated with a particular club as their primary or official home organization.
-
E.
ownerClub
Indicates that a particular club is the owning or parent organization of a given entity (such as a team, facility, or asset).
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f932a248190b65ecfb2bc56e715 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0094af5b481908ad51d5d7ba0c726 |
completed | April 15, 2026, 9:55 p.m. |
Created at: April 10, 2026, 4:45 a.m.