Triple
T13673966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quaker meetings in Britain |
E327823
|
entity |
| Predicate | hasLeadershipModel |
P25067
|
FINISHED |
| Object | non-hierarchical |
—
|
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: non-hierarchical | Statement: [Quaker meetings in Britain, hasLeadershipModel, non-hierarchical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadershipModel Context triple: [Quaker meetings in Britain, hasLeadershipModel, non-hierarchical]
-
A.
hasTypeOfLeadership
chosen
Indicates that an entity possesses or is characterized by a specific style or form of leadership.
-
B.
hasLeaderAndCabinetModel
Indicates that an entity uses a governance structure characterized by a leader (such as a president or prime minister) and an associated cabinet as the primary executive model.
-
C.
hadLeadershipFrom
Indicates that one entity received leadership, guidance, or direction from another entity.
-
D.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
E.
hasCouncilLeaderModel
Indicates that an entity is associated with a specific model or representation of its council leader.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc65aab348190a6611f5765f8392d |
completed | April 12, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.