Triple
T6783194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .sc |
E155734
|
entity |
| Predicate | exampleSecondLevelDomains |
P14826
|
FINISHED |
| Object | .com.sc |
—
|
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: .com.sc | Statement: [.sc, exampleSecondLevelDomains, .com.sc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleSecondLevelDomains Context triple: [.sc, exampleSecondLevelDomains, .com.sc]
-
A.
exampleSecondLevelDomain
chosen
Indicates that one entity is an example of a second-level domain (the part of a domain name directly below a top-level domain) associated with another entity.
-
B.
secondLevelDomain
Indicates that one entity is the second-level domain associated with, or extracted from, another entity such as a full domain name or URL.
-
C.
secondaryDomain
Indicates that one domain functions as a secondary or auxiliary domain in relation to a primary domain.
-
D.
laterDomain
Indicates that one domain or time interval occurs strictly after another in a temporal ordering.
-
E.
internetTLD
Indicates that one entity is the internet top-level domain (TLD) associated with the other 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d289958481908ad4f9467a107083 |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.