Triple
T10041230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College of Europe |
E205298
|
entity |
| Predicate | BrugesCampusSpecialization |
P36070
|
FINISHED |
| Object | European law and economics |
—
|
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: European law and economics | Statement: [College of Europe, BrugesCampusSpecialization, European law and economics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BrugesCampusSpecialization Context triple: [College of Europe, BrugesCampusSpecialization, European law and economics]
-
A.
isSpecializedCampus
chosen
Indicates that a campus is dedicated to a specific field, discipline, or set of specialized programs rather than offering a broad, general curriculum.
-
B.
campusType
Indicates the classification or category of a campus based on its type (e.g., main, satellite, urban, rural).
-
C.
campus1
Indicates a relationship where an entity is identified as a campus or is located on/associated with a particular campus.
-
D.
campus
Indicates that an entity is located on, associated with, or taking place within a particular campus.
-
E.
campusCoreOf
Indicates that one entity serves as the central or primary campus area or component of 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcee2e6d881908cfa0579f9be32e4 |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:55 p.m.