Triple
T2713925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PH Domain Foundation |
E59923
|
entity |
| Predicate | internetCountryCode |
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: [PH Domain Foundation, internetCountryCode, PH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internetCountryCode Context triple: [PH Domain Foundation, internetCountryCode, PH]
-
A.
FIPSCountryCode
Indicates that an entity is associated with a specific country as identified by its FIPS (Federal Information Processing Standards) country code.
-
B.
ISOCode
Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
-
C.
countryCodeTopLevelDomain
chosen
Indicates that a country is associated with a specific top-level internet domain code (ccTLD).
-
D.
associatedCountry
Indicates that there is a relevant connection or linkage between an entity and a specific country, such as origin, operation, or affiliation.
-
E.
ISOCodeContext
Indicates the contextual framework or domain within which a particular ISO code is defined, interpreted, or applied.
- 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda924b24819090adc4128e86d4bd |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8224c688190bb4a362360b03007 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.