Triple
T19655819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hampton High |
E471936
|
entity |
| Predicate | hasLevelAfter |
P47020
|
FINISHED |
| Object | further 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: further education | Statement: [Hampton High, hasLevelAfter, further education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLevelAfter Context triple: [Hampton High, hasLevelAfter, further education]
-
A.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
B.
hasTransitionUpperLevel
Indicates a relationship where something possesses or is associated with an upper-level transition state or phase within a hierarchical or multi-level process.
-
C.
hasSubsequent
chosen
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
-
D.
hasTransitionLowerLevel
Indicates that one state, layer, or condition changes into another that is positioned at a lower level in a hierarchy or scale.
-
E.
followsLevel
Indicates that one entity comes after or succeeds another in a defined sequence, stage, or hierarchical level.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641452ac481908d5493506ee96516 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.