Triple
T15387333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMMI |
E367948
|
entity |
| Predicate | scienceApplication |
P62407
|
FINISHED |
| Object | extragalactic astronomy |
—
|
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: extragalactic astronomy | Statement: [EMMI, scienceApplication, extragalactic astronomy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scienceApplication Context triple: [EMMI, scienceApplication, extragalactic astronomy]
-
A.
aplicación
Indicates that one entity is the use or implementation of another entity for a specific purpose or function.
-
B.
scienceCase
Indicates a relationship where something serves as, constitutes, or provides justification as a scientific case or rationale for a study, hypothesis, or investigation.
-
C.
scienceDomain
chosen
Indicates that one entity is a field, branch, or domain within science to which the other entity is related or belongs.
-
D.
typeOfApplication
Indicates the specific category or kind of application involved in the relationship or action.
-
E.
inventionApplication
Indicates that an entity has submitted or is associated with an application for an invention, typically for legal or patent-related purposes.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e761b688190893a81246b735b76 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.