Triple
T25750620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | InSight |
E648459
|
entity |
| Predicate | HP3Provider |
P51827
|
FINISHED |
| Object | DLR |
—
|
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: DLR | Statement: [InSight, HP3Provider, DLR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HP3Provider Context triple: [InSight, HP3Provider, DLR]
-
A.
typicalProvider
Indicates that one entity commonly or characteristically serves as a provider of goods, services, or resources to another entity.
-
B.
systemPower_hp
Indicates the amount of power, measured in horsepower, that a system produces or requires.
-
C.
providerOf
chosen
Indicates that one entity supplies, furnishes, or makes available a good, service, or resource to another entity.
-
D.
hostIntegration
Indicates a relationship where one system, application, or component is connected and coordinated with a host environment so they can interoperate and exchange functionality or data.
-
E.
hardwarePlatformFor
Indicates that one entity serves as the hardware platform on which another entity is designed to run or be deployed.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd7df2ac8190a206646c8640cec0 |
completed | May 2, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 4:34 a.m.