Triple
T3417788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Western Reporter |
E72050
|
entity |
| Predicate | hasIndexing |
P49340
|
FINISHED |
| Object | headnotes |
—
|
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: headnotes | Statement: [North Western Reporter, hasIndexing, headnotes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndexing Context triple: [North Western Reporter, hasIndexing, headnotes]
-
A.
hasIndex
Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
-
B.
hasListedIndex
Indicates that an entity is associated with a specific index on which it is officially listed or traded.
-
C.
indexingService
Indicates a service that organizes, catalogs, and maintains an index of items or data so they can be efficiently searched and retrieved.
-
D.
hasBaseIndex
Indicates that one entity serves as the reference or starting index from which another entity’s position, offset, or ordering is calculated.
-
E.
hasHIndex
Indicates that an entity (typically a researcher) has a specified h-index value representing their combined publication productivity and citation impact.
- F. None of above. chosen
Provenance (4 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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb92c20fc81909b5debced20ec083 |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb23d23088190aeafe1379eae2eaa |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:15 p.m.