Triple
T11284646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defense Technical Information Center |
E267153
|
entity |
| Predicate | operatesOnInternet |
P39688
|
FINISHED |
| Object | https://discover.dtic.mil/ |
—
|
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: https://discover.dtic.mil/ | Statement: [Defense Technical Information Center, operatesOnInternet, https://discover.dtic.mil/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesOnInternet Context triple: [Defense Technical Information Center, operatesOnInternet, https://discover.dtic.mil/]
-
A.
operatesNetwork
Indicates that an entity manages, controls, or runs the functioning of a network.
-
B.
operatesOnLine
Indicates that an entity conducts operations, services, or activities along a specific line or route.
-
C.
operatedWebsite
chosen
Indicates that one entity runs, manages, or controls the functioning of a particular website.
-
D.
operatesPrimarilyOn
Indicates that one entity is mainly or chiefly used to act upon, affect, or process another entity.
-
E.
isOnLine
Indicates that one entity is located directly along, or in contact with, a specified line or linear path.
- 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9855e8881909bd301718cbd8ca1 |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:31 p.m.