Triple
T30128733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Statistical Society |
E765769
|
entity |
| Predicate | hasLocalGroup |
P76883
|
FINISHED |
| Object | London Local Group |
—
|
NE NERFINISHED |
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: London Local Group | Statement: [Royal Statistical Society, hasLocalGroup, London Local Group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalGroup Context triple: [Royal Statistical Society, hasLocalGroup, London Local Group]
-
A.
hasLocalGroupType
Indicates that an entity is associated with a specific type or category of local group.
-
B.
isInLocalGroupRegion
Indicates that an entity is located within the spatial region associated with the Local Group (the galaxy group containing the Milky Way and its neighbors).
-
C.
isInOutskirtsOfLocalGroupRegion
Indicates that one entity is located in the peripheral or outer boundary region surrounding the Local Group.
-
D.
hasCommunityGroup
chosen
Indicates that an entity is associated with, or belongs to, a specific community group.
-
E.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: April 29, 2026, 7:14 p.m.