Triple
T18501209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tram line 6 (Bern) |
E452068
|
entity |
| Predicate | hasCountryCodeTopLevelDomainContext |
P11776
|
FINISHED |
| Object | .ch |
—
|
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: .ch | Statement: [Tram line 6 (Bern), hasCountryCodeTopLevelDomainContext, .ch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountryCodeTopLevelDomainContext Context triple: [Tram line 6 (Bern), hasCountryCodeTopLevelDomainContext, .ch]
-
A.
countryCodeTopLevelDomain
chosen
Indicates that a country is associated with a specific top-level internet domain code (ccTLD).
-
B.
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).
-
C.
topLevelCountryThen
Indicates that one entity is a top-level country and is followed or succeeded by another entity in a defined sequence or ordering.
-
D.
isCountryCode
Indicates that one entity is a valid country code designating the country represented by the other entity.
-
E.
associatedCountryCode
Indicates that there is a relationship linking something to the country identified by the given country code.
- 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e532c43de48190b49b87c1bb591016 |
completed | April 19, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.