Triple
T24242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRE Transactions on Space Electronics and Telemetry |
E480
|
entity |
| Predicate | scientificDomain |
P934
|
FINISHED |
| Object | engineering |
—
|
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: engineering | Statement: [IRE Transactions on Space Electronics and Telemetry, scientificDomain, engineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scientificDomain Context triple: [IRE Transactions on Space Electronics and Telemetry, scientificDomain, engineering]
-
A.
scientificName
Indicates the formal taxonomic name assigned to an organism according to scientific naming conventions.
-
B.
subjectMatter
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
C.
academicFocus
Indicates the primary field of study, discipline, or subject area that an entity concentrates on academically.
-
D.
fieldOfWork
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
E.
hasResearchArea
chosen
Indicates that an entity (such as a person, project, or organization) is associated with or focused on a particular field or area of research.
- 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_69a243b4ac2c8190b93c303df797b7b2 |
completed | Feb. 28, 2026, 1:24 a.m. |
| NER | Named-entity recognition | batch_69a246e94ca881908f7a7d2c0b293033 |
completed | Feb. 28, 2026, 1:37 a.m. |
| PD | Predicate disambiguation | batch_69a246560af88190961ea00b35cf9388 |
completed | Feb. 28, 2026, 1:35 a.m. |
Created at: Feb. 28, 2026, 1:34 a.m.