Triple
T16284320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian intelligentsia |
E395348
|
entity |
| Predicate | typicalInstitutionalBase |
P49862
|
FINISHED |
| Object | universities |
—
|
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: universities | Statement: [Norwegian intelligentsia, typicalInstitutionalBase, universities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalInstitutionalBase Context triple: [Norwegian intelligentsia, typicalInstitutionalBase, universities]
-
A.
establishedInstitution
Indicates that an entity founded, created, or formally set up an institution or organization.
-
B.
typeOfInstitution
Indicates the specific kind or category of institution that an entity belongs to or is classified as.
-
C.
commonInstitution
Indicates that two or more entities share affiliation with the same institution (such as an organization, school, or company).
-
D.
traditionalInstitution
Indicates that an entity is a long-established, customary organization or system that embodies and maintains traditional practices or norms.
-
E.
typicalBase
chosen
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24912c5808190a0d9c9f491315068 |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.