Triple
T4702963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vratislavia |
E104318
|
entity |
| Predicate | usedAsOfficialName |
P66
|
FINISHED |
| Object | Latin ecclesiastical documents |
—
|
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: Latin ecclesiastical documents | Statement: [Vratislavia, usedAsOfficialName, Latin ecclesiastical documents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsOfficialName Context triple: [Vratislavia, usedAsOfficialName, Latin ecclesiastical documents]
-
A.
officiallyAdopted
Indicates that an entity has been formally accepted, approved, or enacted by an authorized body or process as the recognized standard or version.
-
B.
usedAsOfficialTime
Indicates that something is employed as the recognized standard or authoritative reference for measuring time in an official context.
-
C.
notOfficialNameOf
Indicates that a given name or label is used for an entity but is not its official or formally recognized name.
-
D.
hasOfficialUNName
Indicates that an entity possesses an official name as formally recognized by the United Nations.
-
E.
officialName
chosen
Indicates the formally recognized name assigned to an entity by an authoritative body or source.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650ad0f88190844bfcb46b3071c2 |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd621ba7448190a53ab1e2897acf71 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:17 p.m.