Triple
T29184591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Building 12 |
E739831
|
entity |
| Predicate | hasCleanroom |
P5521
|
FINISHED |
| Object | advanced cleanroom |
—
|
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: advanced cleanroom | Statement: [Building 12, hasCleanroom, advanced cleanroom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCleanroom Context triple: [Building 12, hasCleanroom, advanced cleanroom]
-
A.
hasCleanroomClass
Indicates that an entity is assigned a specific cleanroom classification level according to defined cleanliness or contamination-control standards.
-
B.
hasCleanlinessLevel
Indicates the degree or state of cleanliness associated with an entity.
-
C.
hasCleanVersion
Indicates that an entity is associated with a version that has been cleaned, sanitized, or stripped of unwanted or inappropriate elements.
-
D.
hasRoom
chosen
Indicates that an entity possesses, contains, or is associated with a specific room.
-
E.
hasCleaningFacility
Indicates that an entity provides or is equipped with a facility or service for cleaning.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 28, 2026, 11:59 a.m.