Triple
T30020086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glasgow Shettleston |
E762711
|
entity |
| Predicate | additionalMembersFrom |
P168377
|
FINISHED |
| Object | Glasgow regional list |
—
|
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: Glasgow regional list | Statement: [Glasgow Shettleston, additionalMembersFrom, Glasgow regional list]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: additionalMembersFrom Context triple: [Glasgow Shettleston, additionalMembersFrom, Glasgow regional list]
-
A.
additionalMembersMethod
Indicates the method or process by which additional members are added or included in a group, system, or structure.
-
B.
additionalMembersAllowed
Indicates that more members are permitted to be added beyond those already included or initially specified.
-
C.
numberOfAdditionalMembers
Indicates the count of extra members associated with an entity beyond its primary or standard membership.
-
D.
laterMember
Indicates that one entity became a member of a group or organization at a later time than another entity.
-
E.
includedMembersOf
Indicates that certain members or elements are contained within, or form part of, a specified group or collection.
- F. None of above. chosen
Provenance (4 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67987d8548190ad2276a4bc4c7a10 |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 6:47 p.m.