Triple
T8765680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Career Exploration Program |
E208332
|
entity |
| Predicate | nonBinding |
P13096
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Career Exploration Program, nonBinding, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonBinding Context triple: [Career Exploration Program, nonBinding, true]
-
A.
nonExclusive
Indicates that the relationship or access is shared among multiple parties and is not limited to a single, exclusive holder.
-
B.
binding
Indicates that one entity physically or chemically attaches, adheres, or forms a stable association with another entity.
-
C.
nonVolatile
Indicates that the associated entity or state does not change, disappear, or lose its value when power is removed or over time.
-
D.
nonGovernmental
Indicates that an entity, action, or relationship is not associated with, controlled by, or part of a government or governmental body.
-
E.
isNonBinding
chosen
Indicates that the relationship or agreement exists but does not create any legally or formally enforceable obligation between the involved entities.
- 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_69ca835df7e08190ac875664cca8f9ca |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ee97fd0819087ef8fe14b37ae43 |
completed | March 31, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1884bc8190a46e8308db31f7ab |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:40 p.m.