Triple
T17698764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the community of the Beast Folk |
E441240
|
entity |
| Predicate | enforcesLawThrough |
P128619
|
FINISHED |
| Object | ritual chanting |
—
|
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: ritual chanting | Statement: [the community of the Beast Folk, enforcesLawThrough, ritual chanting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcesLawThrough Context triple: [the community of the Beast Folk, enforcesLawThrough, ritual chanting]
-
A.
enforcedLaw
Indicates that an authority actively applies or upholds a specific law to regulate behavior or resolve situations.
-
B.
enforcement
Indicates the act of compelling compliance with rules, laws, or agreements through monitoring, pressure, or sanctions.
-
C.
typeOfLawEnforcement
Indicates that one entity is a specific kind or category of law enforcement associated with another entity.
-
D.
lawEnforcementFunction
Indicates that an entity performs, is responsible for, or is associated with official law enforcement duties or activities.
-
E.
branchOfLawEnforcementProcess
Indicates that one process is a sub-process, division, or specialized branch within a broader law enforcement process.
- F. None of above. chosen
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_69d8b9ea20b48190ace88bb46b01e6a9 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47158be9c8190bbf4e5162ff74ad2 |
completed | April 19, 2026, 6:08 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:04 a.m.