Triple
T21997544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSAT (General Studies Paper II) |
E543243
|
entity |
| Predicate | weightInFinalRanking |
P107592
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [CSAT (General Studies Paper II), weightInFinalRanking, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightInFinalRanking Context triple: [CSAT (General Studies Paper II), weightInFinalRanking, none]
-
A.
hasOfficialRankingWeight
chosen
Indicates that something carries an officially recognized weight or importance in determining a ranking or ordered list.
-
B.
rankingAtCompletion
Indicates the position or rank an entity holds in an ordered list or competition at the moment the relevant process or event is completed.
-
C.
roleInRanking
Indicates that an entity holds a specific position or function within a particular ranking or ordered list.
-
D.
finalRanking2
Indicates the final ordered position or placement of one entity relative to others in a ranking or competition.
-
E.
rankingPositions
Indicates the ordered placement or level assigned to entities within a ranking or hierarchy.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1276774508190b96870266e10979a |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:19 p.m.