Triple
T5834697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Methodism |
E129438
|
entity |
| Predicate | valuesSourceOfAuthority |
P30515
|
FINISHED |
| Object | Scripture |
—
|
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: Scripture | Statement: [Methodism, valuesSourceOfAuthority, Scripture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valuesSourceOfAuthority Context triple: [Methodism, valuesSourceOfAuthority, Scripture]
-
A.
authorityNamedOn
Indicates that a specific authority or authoritative entity is explicitly identified by name in relation to another entity or record.
-
B.
reputationInSources
Indicates that an entity has a certain reputation or standing as reflected or reported in various information sources.
-
C.
usesAuthorityOf
Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
-
D.
originAssociatedWith
chosen
Indicates a relationship where an entity is connected to, derived from, or influenced by a particular origin, source, or point of beginning.
-
E.
officerSource
Indicates that an officer originates from, is assigned by, or is otherwise sourced from a particular organization, unit, or authority.
- 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.