Triple
T32280330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rappaport's Law |
E824670
|
entity |
| Predicate | stricterThan |
P90714
|
FINISHED |
| Object | International Statute of Wizarding Secrecy |
—
|
NE NERFINISHED |
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: International Statute of Wizarding Secrecy | Statement: [Rappaport's Law, stricterThan, International Statute of Wizarding Secrecy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stricterThan Context triple: [Rappaport's Law, stricterThan, International Statute of Wizarding Secrecy]
-
A.
hasStricterStandardThan
chosen
Indicates that one entity’s rules, criteria, or requirements are more demanding or rigorous than those of another entity.
-
B.
strongerThan
Indicates that one entity possesses greater strength, power, or intensity than another.
-
C.
strictRule
Indicates that a rule is enforced rigidly, allowing no exceptions, flexibility, or deviation in its application.
-
D.
isStrictWith
Indicates that one entity enforces rules, standards, or discipline firmly and without leniency toward another entity.
-
E.
weakerThan
Indicates that one entity has less strength, power, or effectiveness than 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bcc7edfc81909d0008fa9364de54 |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:43 a.m.