Triple
T252657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oliver Brown |
E5183
|
entity |
| Predicate | filedCaseOnBehalfOf |
P4131
|
FINISHED |
| Object | his daughter Linda Brown |
—
|
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: his daughter Linda Brown | Statement: [Oliver Brown, filedCaseOnBehalfOf, his daughter Linda Brown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filedCaseOnBehalfOf Context triple: [Oliver Brown, filedCaseOnBehalfOf, his daughter Linda Brown]
-
A.
legalCase
Indicates a relationship where a formal legal dispute or proceeding exists between parties, typically adjudicated by a court or similar authority.
-
B.
relatedCase
Indicates that one legal case is connected or associated with another case, such as through shared facts, parties, issues, or procedural history.
-
C.
legalSubject
Indicates that an entity is the bearer of legal rights, duties, or responsibilities within a legal relationship or context.
-
D.
defendant
Indicates that an entity is the party accused or sued in a legal action or proceeding.
-
E.
actsOnBehalfOf
chosen
Indicates that one entity performs actions or makes decisions as a representative or proxy 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d39eb3881909f435043c8697f13 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b678d6c81909780e1995c1ca691 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.