Triple
T3820377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GRE Subject Tests |
E84356
|
entity |
| Predicate | statusOfPhysicsTest |
P12388
|
FINISHED |
| Object | discontinued |
—
|
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: discontinued | Statement: [GRE Subject Tests, statusOfPhysicsTest, discontinued]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfPhysicsTest Context triple: [GRE Subject Tests, statusOfPhysicsTest, discontinued]
-
A.
testStatus
chosen
Indicates the current outcome or state of a test, such as whether it has passed, failed, or is still in progress.
-
B.
hasStatusInModernPhysics
Indicates that something holds a particular recognized status or standing within the framework of modern physics.
-
C.
subjectTestsStatus
Indicates that a subject performs a test to determine or verify the status or condition of another entity.
-
D.
testedFor
Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
-
E.
establishedTest
Indicates that an entity has created, set up, or formally instituted a test or testing process.
- 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_69aed931f5908190be2c07af66d4df25 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee74a2bc081909b237df8b1e27653 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.