Triple
T24204702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardcore Holly |
E600073
|
entity |
| Predicate | WWETenureStart |
P18957
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Hardcore Holly, WWETenureStart, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WWETenureStart Context triple: [Hardcore Holly, WWETenureStart, 1994]
-
A.
athleticDirectorTenureStart
Indicates the date or time when an individual begins serving as an athletic director for an organization or institution.
-
B.
initialTenure
Indicates the starting period or first phase of someone’s tenure in a role, position, or organization.
-
C.
notableManagerTenureStart
Indicates the date or point in time when a manager’s particularly significant or distinguished period of managing an entity began.
-
D.
timeInOfficeBeginsIn
chosen
Indicates the point in time or date when an entity’s term, tenure, or period in office starts.
-
E.
tenureType
Indicates the type or category of tenure or contractual engagement that characterizes the relationship between the involved entities.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca52cb881908c99913ea93bc88e |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:37 p.m.