Triple
T4472036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyena-swine |
E98515
|
entity |
| Predicate | tendency |
P19224
|
FINISHED |
| Object | to break The Law of the Beast Folk |
—
|
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: to break The Law of the Beast Folk | Statement: [Hyena-swine, tendency, to break The Law of the Beast Folk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tendency Context triple: [Hyena-swine, tendency, to break The Law of the Beast Folk]
-
A.
hasTendency
chosen
Indicates that an entity is inclined or likely to exhibit a particular behavior, characteristic, or outcome under certain conditions.
-
B.
trends
Indicates that one entity exhibits a general direction of change or development over time in relation to another reference or context.
-
C.
hasTrend
Indicates that something exhibits or is associated with a particular pattern of change or direction over time.
-
D.
ward
Indicates that one entity is under the protection, guardianship, or custodial responsibility of another entity.
-
E.
traction
Indicates the degree to which one entity’s movement or influence effectively grips, pulls, or gains momentum relative to another entity or medium.
- 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356fb69a0819099f0005779f4fcac |
completed | March 13, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69b3563bf4f8819081726cde3a34460b |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:35 p.m.