Triple
T7030442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Level Playing Field Institute |
E163253
|
entity |
| Predicate | outcomeFocus |
P74555
|
FINISHED |
| Object | college readiness in STEM |
—
|
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: college readiness in STEM | Statement: [Level Playing Field Institute, outcomeFocus, college readiness in STEM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeFocus Context triple: [Level Playing Field Institute, outcomeFocus, college readiness in STEM]
-
A.
performanceFocus
Indicates that an entity directs attention or effort toward improving or emphasizing performance in a given context.
-
B.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
-
C.
missionFocus
Indicates that an entity’s primary attention, effort, or resources are directed toward a particular mission, goal, or objective.
-
D.
goals
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
-
E.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
- 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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e458ad9c81908c3f492b317ce291 |
completed | March 27, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b9a2488190aea351d96afa5a12 |
completed | March 27, 2026, 7:59 p.m. |
| PDg | Predicate description generation | batch_69c6e456e89481908df42a1b4232a4a0 |
completed | March 27, 2026, 8:11 p.m. |
Created at: March 27, 2026, 2:35 p.m.