Triple
T1932385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Otis |
E40973
|
entity |
| Predicate | hasCustomers |
P33576
|
FINISHED |
| Object | commercial buildings |
—
|
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: commercial buildings | Statement: [Otis, hasCustomers, commercial buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomers Context triple: [Otis, hasCustomers, commercial buildings]
-
A.
exportCustomer
Indicates initiating the transfer or output of customer-related data from one system or context to another, typically for integration, backup, or reporting purposes.
-
B.
majorCustomer
Indicates that one entity is a primary or high-value customer of another entity, typically contributing a significant portion of business or revenue.
-
C.
hasContractWith
Indicates that one entity is bound by a formal contract or agreement with another entity.
-
D.
hasMarketParticipants
Indicates that a market or trading venue involves or is associated with specific participating entities (such as buyers, sellers, or intermediaries).
-
E.
hasMembers
Indicates that a group, organization, or collection includes certain entities as its members.
- F. None of above. chosen
Provenance (4 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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb297ec2c819092ad62d72005223d |
completed | March 7, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb20c4970819086e66a5435744297 |
completed | March 7, 2026, 5:05 a.m. |
Created at: March 4, 2026, 7:35 p.m.