Triple
T28111222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NTC |
E710492
|
entity |
| Predicate | countryCodeTopLevelDomainOversight |
P11776
|
FINISHED |
| Object | .ph |
—
|
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: .ph | Statement: [NTC, countryCodeTopLevelDomainOversight, .ph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryCodeTopLevelDomainOversight Context triple: [NTC, countryCodeTopLevelDomainOversight, .ph]
-
A.
countryCodeTopLevelDomain
chosen
Indicates that a country is associated with a specific top-level internet domain code (ccTLD).
-
B.
continentCode
Indicates the standardized code assigned to the continent with which an entity is associated.
-
C.
countryDenoted
Indicates that one entity is a name, code, or symbol that specifically refers to or designates a particular country.
-
D.
topLevelCountryThen
Indicates that one entity is a top-level country and is followed or succeeded by another entity in a defined sequence or ordering.
-
E.
countryDeJure
Indicates that one entity is the legally recognized (de jure) country having sovereignty or authority over 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: April 27, 2026, 9:11 p.m.