Triple
T35505947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WISE All-Sky Source Catalog |
E1026150
|
entity |
| Predicate | numberOfSourcesApprox |
P62580
|
FINISHED |
| Object | hundreds of millions |
—
|
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: hundreds of millions | Statement: [WISE All-Sky Source Catalog, numberOfSourcesApprox, hundreds of millions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSourcesApprox Context triple: [WISE All-Sky Source Catalog, numberOfSourcesApprox, hundreds of millions]
-
A.
proposesNumberOfSources
Indicates that an entity suggests or recommends a specific quantity of sources to be used or consulted in a given context.
-
B.
numberOfPointSources
chosen
Indicates the total count of distinct point sources involved or present in a given context or system.
-
C.
mineCountApproximate
Indicates that the number of mines associated with an entity is estimated or roughly counted rather than known exactly.
-
D.
junctionCountApprox
Indicates an approximate count of junctions or connection points involved in or associated with the given entities.
-
E.
numberOfFragmentsApprox
Indicates an approximate count of how many fragments or pieces are associated with the subject.
- 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_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.