Triple
T3517006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superior Court of California, County of Orange |
E74331
|
entity |
| Predicate | hasInterpreterServices |
P41839
|
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: [Superior Court of California, County of Orange, hasInterpreterServices, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInterpreterServices Context triple: [Superior Court of California, County of Orange, hasInterpreterServices, Yes]
-
A.
isInterpretedBy
Indicates that something (such as data, a work, or a signal) is given meaning, understanding, or explanation by a particular agent or process.
-
B.
hasSupportService
chosen
Indicates that one entity provides or is associated with a support-related service for another entity.
-
C.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
D.
hasAPIs
Indicates that one entity provides or exposes application programming interfaces (APIs) that can be used or accessed by another entity.
-
E.
hasInformationService
Indicates that one entity provides, operates, or is associated with an information-related service for 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_69ad85cfb5c881909c9a2edd9d6043cc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc31c0688190a890621a901f5f5f |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae10689c8190b7dc6d7daa8295b6 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.