Triple
T1290274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BIBFRAME |
E27529
|
entity |
| Predicate | hasDocumentationAt |
P28142
|
FINISHED |
| Object | https://www.loc.gov/bibframe/ |
—
|
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: https://www.loc.gov/bibframe/ | Statement: [BIBFRAME, hasDocumentationAt, https://www.loc.gov/bibframe/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDocumentationAt Context triple: [BIBFRAME, hasDocumentationAt, https://www.loc.gov/bibframe/]
-
A.
hasLimitedDocumentation
Indicates that the subject is associated with documentation that is sparse, incomplete, or not sufficiently detailed.
-
B.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
C.
doctypeSyntax
Indicates that one entity specifies or conforms to the syntax rules of a document type declaration (DOCTYPE) used in markup languages.
-
D.
legacyDocumentedBy
Indicates that information about a legacy item or concept is recorded or described in a specific documenting source.
-
E.
hasDescription
Indicates that an entity is associated with a textual description that explains or characterizes it.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0d6af908190ade9c481cc6f0ad8 |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee41ca08190b0ad6f7ea40c0b62 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bfa205ec81909d8170b398345615 |
completed | March 1, 2026, 10:37 p.m. |
Created at: March 1, 2026, 7:51 p.m.