Triple
T4356656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springfield Pride |
E98162
|
entity |
| Predicate | educationalContext |
P55744
|
FINISHED |
| Object | higher education |
—
|
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: higher education | Statement: [Springfield Pride, educationalContext, higher education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: educationalContext Context triple: [Springfield Pride, educationalContext, higher education]
-
A.
educationalFocus
Indicates the primary subject area or theme that an educational activity, program, or resource is centered on.
-
B.
educationalImportance
Indicates the degree to which something is significant, valuable, or impactful in an educational or learning context.
-
C.
educationalImpact
Indicates the effect or influence that one entity has on the learning, knowledge, or educational outcomes of another.
-
D.
educationRight
Indicates that an entity holds a right or entitlement to receive education or educational opportunities.
-
E.
educationUse
Indicates the use or application of something specifically for educational purposes or in an educational context.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351c68a588190ba14a298afacb1dc |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:16 p.m.