Triple
T6666609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andy Pettitte |
E151617
|
entity |
| Predicate | admittedHGHUse |
P72343
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Andy Pettitte, admittedHGHUse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admittedHGHUse Context triple: [Andy Pettitte, admittedHGHUse, yes]
-
A.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
B.
hasAdmission
Indicates that an entity possesses or is associated with a specific admission event, record, or status (such as being admitted to a place, program, or institution).
-
C.
admittedTo
Indicates that one entity has been formally accepted, enrolled, or granted entry into another entity, such as an institution, program, or facility.
-
D.
allegedUse
Indicates that something is claimed or suspected to have been used, without confirming that the use actually occurred.
-
E.
previouslyAdmitted
Indicates that an entity has already been admitted or accepted at an earlier time prior to the current reference point.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6ce72809c8190be85f6e42ca1c8ea |
completed | March 27, 2026, 6:37 p.m. |
Created at: March 27, 2026, 2:02 p.m.