Triple
T675600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pastoral Friends |
E13069
|
entity |
| Predicate | mayIncludePractice |
P2458
|
FINISHED |
| Object | altar calls |
—
|
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: altar calls | Statement: [Pastoral Friends, mayIncludePractice, altar calls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayIncludePractice Context triple: [Pastoral Friends, mayIncludePractice, altar calls]
-
A.
isPracticedBy
Indicates that an activity, skill, or discipline is regularly performed or carried out by a particular entity.
-
B.
stillPracticedIn
Indicates that a tradition, custom, or practice continues to be actively carried out or observed in a specified place or context.
-
C.
associatedWithPractice
chosen
Indicates a relationship in which an entity is connected or linked to a particular practice, activity, or customary way of doing something.
-
D.
requiresLicenseForPractice
Indicates that engaging in the specified professional practice is legally contingent upon holding a valid license.
-
E.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
- 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0266e7c8190a94c4b4b761c59f4 |
completed | March 1, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69a49d1bbd0c81909cfbec30bd17bde7 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.