Triple
T34104323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gustavo Fring |
E874656
|
entity |
| Predicate | hasSuperlab |
P113085
|
FINISHED |
| Object | underground meth superlab |
—
|
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: underground meth superlab | Statement: [Gustavo Fring, hasSuperlab, underground meth superlab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuperlab Context triple: [Gustavo Fring, hasSuperlab, underground meth superlab]
-
A.
superlabLocation
Indicates that one entity is the physical location where a superlab is situated or operates.
-
B.
hasLabAssistant
Indicates that one entity serves as a lab assistant to another entity, typically supporting or assisting in laboratory-related work or activities.
-
C.
hasLaboratorySpace
chosen
Indicates that an entity provides or contains designated laboratory facilities or areas for scientific or technical work.
-
D.
hasLaboratorySystem
Indicates that one entity possesses, uses, or is associated with a particular laboratory system.
-
E.
hasSuperstrate
Indicates that one material, layer, or structure lies above and is supported by another in a layered or composite arrangement.
- 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
Created at: May 1, 2026, 1:53 a.m.