Triple
T17467409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Groningen Centre for Law and Governance |
E425311
|
entity |
| Predicate | hasResearchFocusLevel |
P75955
|
FINISHED |
| Object | national |
—
|
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: national | Statement: [Groningen Centre for Law and Governance, hasResearchFocusLevel, national]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResearchFocusLevel Context triple: [Groningen Centre for Law and Governance, hasResearchFocusLevel, national]
-
A.
hasResearchActivityLevel
chosen
Indicates the degree or intensity of research-related activity associated with an entity.
-
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.
researchFocusSince
Indicates the point in time since which an entity has maintained a particular research focus or area of study.
-
D.
hasResearchOrientation
Indicates that an entity is associated with a particular focus, direction, or approach in its research activities.
-
E.
hasResearched
Indicates that an entity has conducted study, investigation, or systematic inquiry into another entity or topic.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451a8f4908190a67a3a82a1c8f011 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.