Triple
T966610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of New Brunswick |
E20850
|
entity |
| Predicate | isResearchIntensive |
P4469
|
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: [University of New Brunswick, isResearchIntensive, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isResearchIntensive Context triple: [University of New Brunswick, isResearchIntensive, true]
-
A.
researchLevel
chosen
Indicates the degree or stage of research activity, expertise, or advancement associated with an entity in a given context.
-
B.
hasResearchArea
Indicates that an entity (such as a person, project, or organization) is associated with or focused on a particular field or area of research.
-
C.
hasResearchStatus
Indicates that an entity holds a particular stage or condition within a research process, such as planned, in progress, completed, or published.
-
D.
conductsResearchAt
Indicates that a subject carries out research activities at a specified institution, organization, or location.
-
E.
researchStrength
Indicates the degree to which an entity possesses strong capabilities, performance, or impact in conducting research.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b43412488190b68e33d2b36a0ba3 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a42c1481908d940cbe0aefdd3b |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.