Triple
T37848970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okla. Rep. |
E943981
|
entity |
| Predicate | hasReporterTitle |
—
|
GENERATED |
| Object | Oklahoma Reports |
—
|
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: hasReporterTitle Context triple: [Okla. Rep., hasReporterTitle, Oklahoma Reports]
-
A.
hasTitleOver
Indicates that one entity holds a formal title, rank, or designation in relation to another entity.
-
B.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
C.
hasTitleFeature
Indicates that an entity possesses a specific characteristic, attribute, or element related to its title.
-
D.
hasTitleOf
Indicates that one entity holds, bears, or is designated by the official title, name, or rank specified by another entity.
-
E.
hasTitleName
chosen
Indicates that an entity possesses or is associated with a specific title or name.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.