Triple
T18511495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Peden |
E452351
|
entity |
| Predicate | hasNotableFollowers |
P11024
|
FINISHED |
| Object | Scottish Covenanter laity |
—
|
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: Scottish Covenanter laity | Statement: [Alexander Peden, hasNotableFollowers, Scottish Covenanter laity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableFollowers Context triple: [Alexander Peden, hasNotableFollowers, Scottish Covenanter laity]
-
A.
hasFollowers
Indicates that an entity is followed or subscribed to by one or more other entities.
-
B.
estimatedFollowers
Indicates that a numerical value represents an approximation of how many followers an entity has.
-
C.
hasNotableOwner
Indicates that an entity is or has been owned by a person or organization considered notable or significant.
-
D.
layFollowers
chosen
Indicates that one entity is a non-ordained (lay) follower or adherent of another entity, typically a religious figure, institution, or tradition.
-
E.
hasMajorFollowingAmong
Indicates that the subject is widely popular or influential within the specified group or audience.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5334640888190bd44bc15e97822d3 |
completed | April 19, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.