Triple
T679088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Portland |
E13141
|
entity |
| Predicate | strongProgramIn |
P12148
|
FINISHED |
| Object | nursing |
—
|
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: nursing | Statement: [University of Portland, strongProgramIn, nursing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strongProgramIn Context triple: [University of Portland, strongProgramIn, nursing]
-
A.
hasStrongProgramIn
chosen
Indicates that an institution or organization offers a particularly high-quality or well-regarded program in a specified field or area.
-
B.
strength
Indicates the degree of power, intensity, or effectiveness with which an entity can act on, influence, or withstand another entity or force.
-
C.
strengthDescription
Indicates a description or characterization of the degree of strength associated with an entity or relationship.
-
D.
strengthens
Indicates that one entity increases the power, effectiveness, or resilience of another.
-
E.
strengthensFrom
Indicates that one entity becomes stronger, more effective, or more intense as a result of influence, support, or input from another entity.
- 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a04e17088190943d54977eb3f83a |
completed | March 1, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69a49d1d79608190a849ba9ffad2879d |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.