Triple
T26504659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish Biographical Dictionary |
E669511
|
entity |
| Predicate | entryStyle |
P142987
|
FINISHED |
| Object | scholarly |
—
|
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: scholarly | Statement: [Polish Biographical Dictionary, entryStyle, scholarly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryStyle Context triple: [Polish Biographical Dictionary, entryStyle, scholarly]
-
A.
entryMode
chosen
Indicates the manner or method by which something is entered, recorded, or input into a system or context.
-
B.
hasEntranceStyle
Indicates the architectural or design style characterizing the entrance of an entity (such as a building or space).
-
C.
entryFor
Indicates that one entity serves as the specific record, representation, or listing corresponding to another entity.
-
D.
entryDescription
Indicates that a text provides a descriptive summary or explanation of a particular entry or record.
-
E.
entryControl
Indicates a relationship where one entity regulates or authorizes another entity’s access to a place, system, or resource.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6138cc2d48190b30f14187b853bf3 |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:15 a.m.