Triple
T33336404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sombertown |
E853548
|
entity |
| Predicate | lawInForce |
P87698
|
FINISHED |
| Object | ban on toys |
—
|
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: ban on toys | Statement: [Sombertown, lawInForce, ban on toys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lawInForce Context triple: [Sombertown, lawInForce, ban on toys]
-
A.
lawEstablishedBy
Indicates that a particular law was created, enacted, or formally instituted by a specific authority, body, or individual.
-
B.
stateOfLaw
chosen
Indicates that a specified legal condition, rule, or status is currently in force or applicable within a given jurisdiction or context.
-
C.
lawIntroduced
Indicates that a specific law or piece of legislation has been formally proposed or brought forward for consideration within a legislative or governing body.
-
D.
legalAct
Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
-
E.
hasLawEnactedNearby
Indicates that a law has been officially enacted in a location that is geographically close to the referenced 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.