Triple
T32517104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6698 |
E831087
|
entity |
| Predicate | specifiesResourceRecordType |
P2554
|
FINISHED |
| Object | TLSA |
—
|
NE NERFINISHED |
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: TLSA | Statement: [RFC 6698, specifiesResourceRecordType, TLSA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifiesResourceRecordType Context triple: [RFC 6698, specifiesResourceRecordType, TLSA]
-
A.
specType
Indicates the specific type or category of a specification that an entity is associated with.
-
B.
specifiesMethod
Indicates that one entity defines or designates the particular method or procedure by which another entity operates or is carried out.
-
C.
referenceType
Indicates the specific kind or category of reference relationship that one entity has to another.
-
D.
recordTypeCode
Indicates the specific classification or category assigned to a record within a system or dataset.
-
E.
hasRecordType
chosen
Indicates that an entity is associated with or classified under a specific type or category of record.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1 a.m.