Triple
T24822271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CGS-EMU system |
E621092
|
entity |
| Predicate | usesSubsystem |
P162065
|
FINISHED |
| Object | electromagnetic (EMU) subsystem |
—
|
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: electromagnetic (EMU) subsystem | Statement: [CGS-EMU system, usesSubsystem, electromagnetic (EMU) subsystem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSubsystem Context triple: [CGS-EMU system, usesSubsystem, electromagnetic (EMU) subsystem]
-
A.
usesEntrySystem
Indicates that an entity operates or interacts through a particular entry or access control system.
-
B.
usedBySystem
Indicates that something is utilized or operated by a particular system.
-
C.
usesSubgroup
Indicates that one entity employs, incorporates, or operates through a specific subgroup of another entity or system.
-
D.
usesDataSystem
Indicates that one entity employs, accesses, or relies on a particular data system to perform its functions or operations.
-
E.
usesForces
Indicates that one entity applies physical, magical, or other types of forces to influence, move, or affect another entity.
- F. None of above. chosen
Provenance (4 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 18, 2026, 5:04 a.m.