Triple
T6828851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Thread |
E157084
|
entity |
| Predicate | investigationStyle |
P22717
|
FINISHED |
| Object | multi-source reporting |
—
|
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: multi-source reporting | Statement: [The Thread, investigationStyle, multi-source reporting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: investigationStyle Context triple: [The Thread, investigationStyle, multi-source reporting]
-
A.
investigativeFocus
Indicates that an entity is the primary subject or target of investigation, inquiry, or detailed scrutiny by another entity.
-
B.
usesInvestigativeMethods
chosen
Indicates that an entity employs investigative techniques or procedures to gather information, analyze evidence, or uncover facts.
-
C.
investigatedBy
Indicates that an entity is the subject of an investigation carried out by another entity.
-
D.
settingOfInvestigation
Indicates the context, environment, or circumstances in which an investigation takes place.
-
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_69c6882a5b5c8190917a7db9ed36bad1 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d6254bd88190a2a424537c2c12e2 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.