Triple
T204388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cranch |
E4578
|
entity |
| Predicate | reporterNameUsedIn |
P2937
|
FINISHED |
| Object | nominative citation |
—
|
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: nominative citation | Statement: [Cranch, reporterNameUsedIn, nominative citation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reporterNameUsedIn Context triple: [Cranch, reporterNameUsedIn, nominative citation]
-
A.
reporterType
Indicates the specific role or category of reporter associated with an entity or event.
-
B.
reporter
Indicates that an entity acts in the role of a reporter, typically gathering, writing, or presenting information or news about another entity or event.
-
C.
reporterStyle
Indicates that one entity presents information in the manner or stylistic approach characteristic of a reporter or journalistic reporting.
-
D.
hasOfficialReporter
Indicates that something (such as a case, decision, or proceeding) is associated with an officially designated reporter or publication that records it.
-
E.
nameUsedBy
chosen
Indicates that a particular name is employed or referenced by a specific entity.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f46b4f081909e5ee3718109a71f |
completed | Feb. 28, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69a25b4b42ec8190bef16bbbdd30a742 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.