Triple
T4420216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bertramus |
E95078
|
entity |
| Predicate | hasNameFormType |
P1081
|
FINISHED |
| Object | scholarly form |
—
|
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 form | Statement: [Bertramus, hasNameFormType, scholarly form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameFormType Context triple: [Bertramus, hasNameFormType, scholarly form]
-
A.
hasTypeName
Indicates that an entity is associated with a specific type name used to classify or identify its kind.
-
B.
hasNameFunction
Indicates that an entity is associated with a function whose purpose is to provide or determine its name.
-
C.
nameType
chosen
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
-
D.
hasForm
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
E.
hasSurnameType
Indicates that an entity’s surname belongs to a particular category or type (e.g., patronymic, toponymic, occupational).
- 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3551fae7c8190abafda0d78f02d89 |
completed | March 13, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.