Triple
T18299242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish universities |
E438310
|
entity |
| Predicate | includeGroup |
P10571
|
FINISHED |
| Object | ancient universities of Scotland |
—
|
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: ancient universities of Scotland | Statement: [Scottish universities, includeGroup, ancient universities of Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeGroup Context triple: [Scottish universities, includeGroup, ancient universities of Scotland]
-
A.
includesCommonGroups
Indicates that two entities share at least one group or category in common.
-
B.
usesGroup
Indicates that an entity makes use of, operates with, or relies on a particular group as a collective resource, tool, or participant in some activity or process.
-
C.
containsGroup
chosen
Indicates that one entity includes or encompasses a specific group of entities within it.
-
D.
identifiesGroup
Indicates that one entity serves to recognize, label, or distinguish another entity as belonging to a particular group or category.
-
E.
includedBy
Indicates that one entity is contained within, encompassed by, or treated as a subset or member 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017d96588190ac1e326803142976 |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.