Triple
T35505958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WISE All-Sky Source Catalog |
E1026150
|
entity |
| Predicate | dataProductsInclude |
P44684
|
FINISHED |
| Object | astrometry |
—
|
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: astrometry | Statement: [WISE All-Sky Source Catalog, dataProductsInclude, astrometry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataProductsInclude Context triple: [WISE All-Sky Source Catalog, dataProductsInclude, astrometry]
-
A.
productIncludes
chosen
Indicates that a product contains, comprises, or is composed of the specified component, item, or feature.
-
B.
productWith
Indicates a relationship where one entity is associated with, contains, or is offered together with another entity as a product.
-
C.
productFor
Indicates that one entity is intended to be used by, with, or in relation to another entity as its product or offering.
-
D.
byProduct
Indicates that one entity is produced incidentally or as a secondary result of a process, activity, or creation involving another entity.
-
E.
marketIncludes
Indicates that a given market contains, offers, or encompasses a specified product, service, or segment as part of its scope.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.