Triple
T8208951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Business Law Transactions Clinic |
E191763
|
entity |
| Predicate | clientTypeServed |
P79955
|
FINISHED |
| Object | real-world clients |
—
|
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: real-world clients | Statement: [Business Law Transactions Clinic, clientTypeServed, real-world clients]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clientTypeServed Context triple: [Business Law Transactions Clinic, clientTypeServed, real-world clients]
-
A.
operatedForClientType
Indicates that an operation or service is performed specifically on behalf of, or tailored to, a particular type or category of client.
-
B.
clientOf
Indicates that one entity receives services or conducts business from another entity in a client–provider relationship.
-
C.
usesServerType
Indicates that an entity operates on, is hosted by, or otherwise relies on a specific type or category of server.
-
D.
hasNotableClientType
chosen
Indicates that an entity has clients belonging to a particular notable or distinguished category or type.
-
E.
siteTypeServed
Indicates the type of site or location that is served, supported, or handled by a given entity or resource.
- 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_69ca82c7f3e08190857bf1fc63b2a10c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb76dc784881908e1f63ac907cdd01 |
completed | March 31, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:44 p.m.