Triple
T33727543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Real Transported Man |
E864183
|
entity |
| Predicate | secretInvestigatedBy |
P6157
|
FINISHED |
| Object | Alfred Borden |
—
|
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: Alfred Borden | Statement: [The Real Transported Man, secretInvestigatedBy, Alfred Borden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secretInvestigatedBy Context triple: [The Real Transported Man, secretInvestigatedBy, Alfred Borden]
-
A.
investigatedBy
chosen
Indicates that an entity is the subject of an investigation carried out by another entity.
-
B.
investigatedFor
Indicates that an entity is the subject of an investigation concerning a suspected involvement in another entity (typically a crime, incident, or wrongdoing).
-
C.
subjectOfInquest
Indicates that an entity is the focus or target of a formal inquest or official investigative proceeding.
-
D.
commissionInvestigated
Indicates that a commission formally examined, inquired into, or investigated a particular matter or entity.
-
E.
investigatedUsing
Indicates that an investigation, study, or analysis was carried out by means of a specified method, tool, 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:44 a.m.