Triple
T441626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .phl |
E10124
|
entity |
| Predicate | proposedForUseAs |
P12134
|
FINISHED |
| Object | internet country code top-level domain |
—
|
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: internet country code top-level domain | Statement: [.phl, proposedForUseAs, internet country code top-level domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedForUseAs Context triple: [.phl, proposedForUseAs, internet country code top-level domain]
-
A.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
B.
plannedUseOf
chosen
Indicates that one entity is intended or designated to be used for a specific purpose, function, or activity involving another entity.
-
C.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
D.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
E.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef42b4008190abed9d79926c7022 |
completed | Feb. 28, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69a2eddcf50c8190bfa0d1f8ee9f604a |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.