Triple
T2391149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Punu |
E48945
|
entity |
| Predicate | GuthrieClassification |
P18539
|
FINISHED |
| Object | B.40 |
—
|
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: B.40 | Statement: [Punu, GuthrieClassification, B.40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GuthrieClassification Context triple: [Punu, GuthrieClassification, B.40]
-
A.
guthrieClassification
chosen
Indicates a categorization relationship where an entity is assigned a class or type according to the Guthrie classification system.
-
B.
governingClassification
Indicates the classification system or category framework that determines how an entity is organized, labeled, or regulated.
-
C.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
D.
isClassifiedUnder
Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
-
E.
libraryOfCongressClassification
Indicates that one entity is assigned a Library of Congress Classification code that organizes it within the Library of Congress subject-based cataloging system.
- 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc87457388190822d5506327db8f2 |
completed | March 7, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.