Triple
T4787005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogan & Hartson |
E106502
|
entity |
| Predicate | servedClientsIn |
P35093
|
FINISHED |
| Object | public 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: public sector | Statement: [Hogan & Hartson, servedClientsIn, public sector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedClientsIn Context triple: [Hogan & Hartson, servedClientsIn, public sector]
-
A.
servedUntil
Indicates the ending time or date up to which an entity held a position, role, or service.
-
B.
clientOf
chosen
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
C.
servedTimeAt
Indicates the specific time period during which an entity was served or received service at a particular place or context.
-
D.
servedDuring
Indicates that one entity held a role, position, or performed a function within the time period defined by another entity.
-
E.
servesLineSince
Indicates that a transportation service or route has been operating on a particular line since a specified point in time.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65d8f9d881909c24340b8dc6a104 |
completed | March 20, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.