Triple
T13179923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA Extragalactic Database |
E313694
|
entity |
| Predicate | integratesDataFrom |
P1075
|
FINISHED |
| Object | astronomical surveys |
—
|
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: astronomical surveys | Statement: [NASA Extragalactic Database, integratesDataFrom, astronomical surveys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratesDataFrom Context triple: [NASA Extragalactic Database, integratesDataFrom, astronomical surveys]
-
A.
integratedFrom
Indicates that something has been formed or constructed by combining or incorporating elements originating from another source.
-
B.
integrationDate
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
-
C.
integrates
chosen
Indicates that one entity combines or brings together another entity or set of entities into a unified, functioning whole.
-
D.
collectsDataFor
Indicates that one entity gathers or records data on behalf of, or for the benefit of, another entity.
-
E.
integratedDate
Indicates the date on which one entity was incorporated, combined, or brought into a larger system or whole.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.