Triple
T32512858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Squishee |
E830981
|
entity |
| Predicate | inUniverseRegulationStatus |
P29456
|
FINISHED |
| Object | poorly regulated |
—
|
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: poorly regulated | Statement: [Squishee, inUniverseRegulationStatus, poorly regulated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseRegulationStatus Context triple: [Squishee, inUniverseRegulationStatus, poorly regulated]
-
A.
regulationStatus
chosen
Indicates the regulatory condition or compliance state that applies to an entity under relevant rules or laws.
-
B.
inUniverseRestriction
Indicates that something is limited, applicable, or valid only within a specific fictional or defined universe or continuity.
-
C.
legalStatusInUniverse
Indicates the formal legal standing or classification an entity holds within a specified fictional or conceptual universe.
-
D.
inUniverseUseRestriction
Indicates that the use of something is restricted or limited within a specific fictional or defined universe or setting.
-
E.
hasRegulatedBy
Indicates that one entity is subject to control, governance, or rules imposed by 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: May 1, 2026, 1 a.m.