Triple
T37572019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brigada |
E934713
|
entity |
| Predicate | hasReportingStyle |
—
|
GENERATED |
| Object | field reporting |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReportingStyle Context triple: [Brigada, hasReportingStyle, field reporting]
-
A.
reportingStyle
chosen
Indicates the manner or approach an entity uses when presenting or communicating information, such as tone, structure, or level of detail in its reports.
-
B.
hasReportingMarkFormat
Indicates that one entity’s reporting mark follows or conforms to the specified format or pattern defined by the other entity.
-
C.
reporterStyle
Indicates that one entity presents information in the manner or stylistic approach characteristic of a reporter or journalistic reporting.
-
D.
hasStyle
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
E.
hasReportingNameType
Indicates that an entity is associated with a specific type or category of reporting name used to identify it in reports or documentation.
- F. None of above.
Provenance (1 batch)
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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.