Triple
T18798438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Technical Information Service |
E459697
|
entity |
| Predicate | operatesDatabase |
P5884
|
FINISHED |
| Object | NTIS bibliographic database |
—
|
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: NTIS bibliographic database | Statement: [National Technical Information Service, operatesDatabase, NTIS bibliographic database]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesDatabase Context triple: [National Technical Information Service, operatesDatabase, NTIS bibliographic database]
-
A.
operatesBase
Indicates that an organization or agent runs or manages a primary facility, location, or base of operations.
-
B.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
C.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
D.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
-
E.
operatesService
chosen
Indicates that an agent runs, manages, or provides a particular service.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a0215084819086bce60f95d08409 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.