Triple
T22749528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R179 |
E562655
|
entity |
| Predicate | hasIntercomSystem |
P148437
|
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: [R179, hasIntercomSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntercomSystem Context triple: [R179, hasIntercomSystem, yes]
-
A.
hasEmergencyIntercoms
Indicates that an entity is equipped with emergency intercom devices available for use in urgent or crisis situations.
-
B.
hasIntruderDetectionSystem
Indicates that an entity is equipped with a system designed to detect unauthorized or intruding entities.
-
C.
hasChimes
Indicates that one entity possesses or is equipped with chimes as a feature or component.
-
D.
hasIntegratedUnit
Indicates that one entity includes another entity as a built-in or internally combined component or unit.
-
E.
hasCommunicationAccess
chosen
Indicates that one entity is able to communicate with, or use a communication channel or service provided 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179b822988190b5368ac1f4e1d70a |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:24 p.m.