Triple
T15760038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jones Lang LaSalle |
E382071
|
entity |
| Predicate | servesClientsIn |
P120222
|
FINISHED |
| Object | office real estate sector |
—
|
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: office real estate sector | Statement: [Jones Lang LaSalle, servesClientsIn, office real estate sector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesClientsIn Context triple: [Jones Lang LaSalle, servesClientsIn, office real estate sector]
-
A.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
B.
servesUsers
Indicates that an entity provides services, functionality, or benefits to one or more users.
-
C.
servesOn
Indicates that one entity performs duties, functions, or holds a role as a member within another entity, such as a group, body, or organization.
-
D.
servesCustomer
Indicates that one entity provides service, assistance, or products to another entity in the role of a customer.
-
E.
servesUsersFrom
Indicates that an entity provides services or resources to users originating from or associated with a specified source or location.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b52c548190a0ffa4493a4eb15c |
completed | April 16, 2026, 3 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e03cc871d0819085c0fc54de7984ff |
completed | April 16, 2026, 1:35 a.m. |
Created at: April 10, 2026, 4:47 a.m.