Triple
T24440286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benedictine monastery in Mogilno |
E616238
|
entity |
| Predicate | topLevelDomainForWebsite |
P11776
|
FINISHED |
| Object | .pl |
—
|
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: .pl | Statement: [Benedictine monastery in Mogilno, topLevelDomainForWebsite, .pl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topLevelDomainForWebsite Context triple: [Benedictine monastery in Mogilno, topLevelDomainForWebsite, .pl]
-
A.
hasTopLevelDomain
Indicates that one entity (typically a website, domain name, or internet resource) is associated with a specific top-level domain (such as .com, .org, or .uk).
-
B.
countryCodeTopLevelDomain
chosen
Indicates that a country is associated with a specific top-level internet domain code (ccTLD).
-
C.
TLDType
Indicates the classification or category of a top-level domain (TLD) based on its intended purpose or administrative type.
-
D.
internetTLD
Indicates that one entity is the internet top-level domain (TLD) associated with the other entity.
-
E.
territorialDomain
Indicates that one entity has territorial authority, control, or jurisdiction over a geographic area or domain associated with another entity.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2978a5cac81909d2141b606714fd4 |
completed | April 29, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:17 a.m.