Triple
T18977808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanford Cardinal women’s tennis |
E464341
|
entity |
| Predicate | individualHonors |
P17372
|
FINISHED |
| Object | multiple All-American players |
—
|
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: multiple All-American players | Statement: [Stanford Cardinal women’s tennis, individualHonors, multiple All-American players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: individualHonors Context triple: [Stanford Cardinal women’s tennis, individualHonors, multiple All-American players]
-
A.
nameHonors
Indicates that a name is given to honor, commemorate, or pay tribute to a particular entity.
-
B.
honoursAchievement
Indicates that one entity formally recognizes and celebrates the notable accomplishment or success of another entity.
-
C.
includesHonoraryAwardsFor
Indicates that one entity contains or lists honorary awards that have been granted to another entity.
-
D.
honors
Indicates that one entity shows respect, recognition, or esteem toward another entity, often in a formal or ceremonial way.
-
E.
awardOrRanking
chosen
Indicates that there is an award, honor, or ranking status conferred on or associated with an 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d620bba48190a300dba9733592b0 |
completed | April 20, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon