Triple
T30834899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latapie House |
E785332
|
entity |
| Predicate | hasTransparentEnvelope |
P189111
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Latapie House, hasTransparentEnvelope, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransparentEnvelope Context triple: [Latapie House, hasTransparentEnvelope, yes]
-
A.
isTransparent
chosen
Indicates that one entity allows light or information to pass through it such that other entities behind or within it can be clearly perceived.
-
B.
hasTransparencyRequirement
Indicates that one entity is obligated to provide clear, accessible information or disclosure to another entity or to the public.
-
C.
isTransparentTo
Indicates that one entity allows another entity (such as light, information, or influence) to pass through or be perceived without obstruction or concealment.
-
D.
isOpaque
Indicates that one entity does not allow light or visual information to pass through it, preventing clear or any visibility of what is behind or within it.
-
E.
hasEnvelopeShapes
Indicates that one entity possesses or is characterized by specific envelope-like shapes associated with 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_69f224b73d8c81908129383bfb397c87 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: April 29, 2026, 8:45 p.m.