Triple
T7675224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selective High School Placement Test |
E173843
|
entity |
| Predicate | isHighStakes |
P78860
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Selective High School Placement Test, isHighStakes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHighStakes Context triple: [Selective High School Placement Test, isHighStakes, true]
-
A.
featuresHighStakesGames
Indicates that something includes or offers games involving significant risk, tension, or major consequences for the participants.
-
B.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
C.
isHighlyPrized
Indicates that something is regarded with exceptional value, admiration, or importance, often being especially sought after or cherished.
-
D.
isHighRanking
Indicates that an entity holds a position of relatively great authority, status, or seniority within a hierarchy or organization.
-
E.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
- 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_69c6995703e0819081de77361b602e78 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69c7048a01508190bc2e9ae8b863486c |
completed | March 27, 2026, 10:28 p.m. |
Created at: March 27, 2026, 4:01 p.m.