Triple
T8451491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .tf |
E199808
|
entity |
| Predicate | zoneFileAvailable |
P82709
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [.tf, zoneFileAvailable, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneFileAvailable Context triple: [.tf, zoneFileAvailable, yes]
-
A.
ianaZoneFile
Indicates that an entity is associated with, defined by, or described in a specific IANA DNS zone file.
-
B.
DNSZone
Indicates a relationship where a set of DNS records is grouped and managed together under a specific domain namespace as a single administrative unit.
-
C.
isCanonicalZone
Indicates that a given zone is the primary, standard, or officially recognized version among possible alternatives.
-
D.
zoneManagedFrom
Indicates that a particular zone or area is administered, controlled, or overseen from a specified location or managing entity.
-
E.
canExistAt
Indicates that an entity is capable of being present or occurring at a specified location, time, or context.
- F. None of above. chosen
Provenance (4 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_69ca8318231881908fd1bc1c4d45d286 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe44815488190a912d63512e19af0 |
completed | March 31, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:09 p.m.