Triple
T35013596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Pact |
E1009995
|
entity |
| Predicate | primaryFollowers |
P156817
|
FINISHED |
| Object | Bosmer |
E1014621
|
NE 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: Bosmer | Statement: [Green Pact, primaryFollowers, Bosmer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFollowers Context triple: [Green Pact, primaryFollowers, Bosmer]
-
A.
layFollowers
Indicates that one entity is a non-ordained (lay) follower or adherent of another entity, typically a religious figure, institution, or tradition.
-
B.
hasPrimaryFollowers
chosen
Indicates that an entity is the main or principal object of following, attention, or allegiance for one or more other entities.
-
C.
primaryMembers
Indicates that the related entities are the main or most important members within a larger group or organization.
-
D.
followersFrom
Indicates that one entity follows or originates from another entity, typically representing a following relationship based on source or origin.
-
E.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
- F. None of above.
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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3efd92fb7c81909a501a96a32f7255 |
completed | June 26, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.