Triple
T35198309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andrew Neiman |
E1016328
|
entity |
| Predicate | filesComplaintAgainst |
P30230
|
FINISHED |
| Object | Terence Fletcher |
—
|
NE NERFINISHED |
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: Terence Fletcher | Statement: [Andrew Neiman, filesComplaintAgainst, Terence Fletcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filesComplaintAgainst Context triple: [Andrew Neiman, filesComplaintAgainst, Terence Fletcher]
-
A.
complainedTo
Indicates that one entity expressed dissatisfaction, criticism, or a grievance directly to another entity.
-
B.
filedWith
chosen
Indicates that one entity has officially submitted or registered something (such as a document, complaint, or application) to another entity or authority.
-
C.
filesReport
Indicates that one entity submits or delivers an official report or document to another entity or authority.
-
D.
complainsAbout
Indicates that one entity expresses dissatisfaction, criticism, or grievances regarding another entity or situation.
-
E.
legalClaimBy
Indicates that a specific party initiates or holds a legal claim against another party or concerning a particular matter.
- 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78e331ab08190966ad7ec0ec8d846 |
completed | May 3, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.